From owner-ietf-ppp@merit.edu Mon Aug 12 10:20:42 2002 Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23725 for ; Mon, 12 Aug 2002 10:20:42 -0400 (EDT) Received: by trapdoor.merit.edu (Postfix) id 046DF9120A; Mon, 12 Aug 2002 10:21:41 -0400 (EDT) Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id C886491267; Mon, 12 Aug 2002 10:21:40 -0400 (EDT) Delivered-To: ietf-ppp@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id ABFAF9120A for ; Mon, 12 Aug 2002 10:21:39 -0400 (EDT) Received: by segue.merit.edu (Postfix) id 9127B5DE07; Mon, 12 Aug 2002 10:21:39 -0400 (EDT) Delivered-To: ietf-ppp@merit.edu Received: from exchange.Ic4ic.com (unknown [194.90.135.194]) by segue.merit.edu (Postfix) with SMTP id E304B5DDE0 for ; Mon, 12 Aug 2002 10:21:38 -0400 (EDT) Received: through eSafe SMTP Relay 1028634880; Mon Aug 12 17:22:10 2002 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C24213.E5FF2C34" Subject: Self-Describing-Padding, RFC 1990 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Mon, 12 Aug 2002 17:21:15 +0200 Message-ID: <88BC9E379956AE4DB689CC5FF6F5A43D307EA4@exchange.Ic4ic.com> Thread-Topic: Self-Desribibg-Padding, RFC 1990 Thread-Index: AcJB5cb9CuKGerKsT3qAMukKzZBfHwALXRuQAAAZcTA= From: "Daniel Feldman" To: Cc: "Naim Far" Sender: owner-ietf-ppp@merit.edu Precedence: bulk Errors-To: owner-ietf-ppp-outgoing@merit.edu This is a multi-part message in MIME format. ------_=_NextPart_001_01C24213.E5FF2C34 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable > -----Original Message----- > From: Naim Far =20 > Sent: Monday, August 12, 2002 11:51 AM > To: 'ietf-ppp@merit.edu' > Subject: Self-Describing-Padding, RFC 1990 >=20 > Hi, > There something that I don't understand with RFC 1990: > In section 2 (General Overview) it is specifically written that the option of No Self-Describing-Padding has to be manually configured within the encapsulation of the packets, while in section 3.1. (Padding Considerations) it's written "Systems that support the multilink protocol SHOULD implement Self- Describing-Padding". I think it's a mistake in the document. ------_=_NextPart_001_01C24213.E5FF2C34 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Cc: , "Naim Far" Subject: Re: Self-Describing-Padding, RFC 1990 In-Reply-To: Daniel Feldman's message of 12 August 2002 17:21:15 References: <88BC9E379956AE4DB689CC5FF6F5A43D307EA4@exchange.Ic4ic.com> X-Mailer: VM 7.01 under Emacs 21.2.1 Sender: owner-ietf-ppp@merit.edu Precedence: bulk Errors-To: owner-ietf-ppp-outgoing@merit.edu Content-Transfer-Encoding: 7bit Daniel Feldman writes: > > There something that I don't understand with RFC 1990: > > In section 2 (General Overview) it is specifically > written that the option of No Self-Describing-Padding has to be manually > configured within the encapsulation of the packets, while in section > 3.1. (Padding Considerations) it's written "Systems that support the > multilink protocol SHOULD implement Self- Describing-Padding". I think > it's a mistake in the document. I think you're confusing two separate things. The packets at the bundle level (that is, before fragmentation and after reassembly) must not be padded in any way. That's what the note in section 2 means. The note in section 3.1 is referring to how the fragments themselves are actually carried on the links. These may be padded if necessary, and if any padding at all is needed, then SDP must be used. In other words, padding is a per-link issue, not a per-bundle issue. (All that said, implementation of SDP and the need for padding at all are so rare that doing without is probably the best course for most implementors.) -- James Carlson, Solaris Networking SUN Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677