RE: [PWE3] draft-ietf-pwe3-iana-allocation-12.txt LAST CALL
"Ash, Gerald R \(Jerry\), ALABS" <gash@att.com> Wed, 21 September 2005 11:53 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EI39z-0007jF-4u; Wed, 21 Sep 2005 07:53:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EI39w-0007j2-VP for pwe3@megatron.ietf.org; Wed, 21 Sep 2005 07:53:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13920 for <pwe3@ietf.org>; Wed, 21 Sep 2005 07:53:07 -0400 (EDT)
Received: from mail121.messagelabs.com ([216.82.241.195]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EI3Fw-0007QD-1i for pwe3@ietf.org; Wed, 21 Sep 2005 07:59:22 -0400
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-3.tower-121.messagelabs.com!1127303530!5926421!14
X-StarScan-Version: 5.4.15; banners=-,-,-
X-Originating-IP: [192.128.133.132]
Received: (qmail 28984 invoked from network); 21 Sep 2005 11:52:56 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (192.128.133.132) by server-3.tower-121.messagelabs.com with SMTP; 21 Sep 2005 11:52:56 -0000
Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by attrh3i.attrh.att.com (7.2.052) id 431D9D370023B40A; Wed, 21 Sep 2005 07:52:55 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] draft-ietf-pwe3-iana-allocation-12.txt LAST CALL
Date: Wed, 21 Sep 2005 06:52:54 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA9382@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: [PWE3] draft-ietf-pwe3-iana-allocation-12.txt LAST CALL
Thread-Index: AcW9Jnx5xaRv+TotTzeTAbFJ+yAdJgBde2AQ
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: Luca Martini <lmartini@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Content-Transfer-Encoding: quoted-printable
Cc: "Malis, Andrew G." <Andy.Malis@Tellabs.com>, "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, pwe3 <pwe3@ietf.org>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
Hi Luca, > Jerry, let's finish the e-mail discussion anyway, then all > you have to do is mention the registry name from the pwe3 > IANA draft, and ask for allocation from IANA in your draft. OK, sounds good. > Can you actually specify the length of this parameter? > If you read the iana allocation draft carefully , you'll > notice that "variable length" is not a choice. This is > because of some concerns that this sub-tlv could be abused > and cause LDP to store large amount of information. > I will have a look at the RFC mentioned as well, but I > would like to point out that the interface parameter > Sub-TLV can only be sent once in the lifetime of the PW. > (changing the value of it means tearing down the PW , and > starting over). We'll specify a fixed length (TBD) for each of the two requested Interface Parameters Sub-TLV code-points. Here are some further details and background on the request: In Section 4.1 of http://ietf.org/internet-drafts/draft-ietf-avt-hc-over-mpls-protocol-00. txt we say "The Interface Parameters Sub-TLV [IANA, PW-SIG], illustrated in Figure 4, is used to signal HC (header compression) session setup and HC parameter negotiation, such as described for HC-over-PPP mechanisms [RFC3241, RFC3544]. The principles and IPCP messages described in [RFC3241, RFC3544] are reused to enable PW/MPLS HC session configuration, as the PPP layer does for each of the HC mechanisms." That is, we're using the Interface Parameters Sub-TLV to negotiate header compression session setup and parameter negotiation. We're requesting 2 code-points: one for the network control protocol (NCP) for IPv4, IPCP [RFC1332], and one for the IPv6 NCP, IPV6CP [RFC2472], as follows: 0x?? Length TBD IPCP [RFC1332] 0x?? Length TBD IPV6CP [RFC2472] Within the Interface Parameters Sub-TLV, we further encode each header compression setup/parameter-negotiation TLV identified in RFC 3251 and RFC 3544. For example, in RFC 3544 http://www.ietf.org/rfc/rfc3544.txt?number=3544, we encode the RTP sub-options (Section 2.2) and ECRTP sub-options (Section 2.3) within the NCP format specified in Section 2.1: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | IP-Compression-Protocol | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | TCP_SPACE | NON_TCP_SPACE | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | F_MAX_PERIOD | F_MAX_TIME | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MAX_HEADER | suboptions... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ We'll specify a fixed length (TBD) for each of the two interface parameter types, as required, using the maximum length across all the sub-options identified in RFC 3251 and RFC 3544, and then use blank bytes in the encoding of each sub-option, as needed. Please let us know of any further comments or suggestions on the request. Thanks, Regards, Jerry > Ash, Gerald R (Jerry), ALABS wrote: > > >Stewart, > >Luca, > > > >We want to request 2 additional code points, as specified in the IANA > >Section 7 of > >http://ietf.org/internet-drafts/draft-ietf-avt-hc-over-mpls-protocol-00 .txt. > > > >In particular, the following is requested: > > > >7. IANA Considerations > > > > As discussed in Section 4.1, Pseudowire Interface Parameter > > Sub-TLV type values need to be specified by IANA for both the > > network control protocol for IPv4, IPCP [RFC1332] and the > > IPv6 NCP, IPV6CP [RFC2472], as follows: > > > > 0x?? Variable Length IPCP [RFC1332] > > 0x?? Variable Length IPV6CP [RFC2472] > > > >Thanks, > >Jerry > > > >-----Original Message----- > >From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] > On Behalf Of > >Stewart Bryant > >Sent: Monday, September 19, 2005 9:46 AM > >To: pwe3 > >Subject: [PWE3] draft-ietf-pwe3-iana-allocation-12.txt LAST CALL > > > >This is the start of a one week WG last call on > > > >http://www.ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-12. txt > > > >Last call will end 0900 GMT on Tuesday 27th September 2005. > > > >- Stewart _______________________________________________ pwe3 mailing list pwe3@ietf.org https://www1.ietf.org/mailman/listinfo/pwe3
- [PWE3] draft-ietf-pwe3-iana-allocation-12.txt LAS… Stewart Bryant
- RE: [PWE3] draft-ietf-pwe3-iana-allocation-12.txt… Ash, Gerald R (Jerry), ALABS
- Re: [PWE3] draft-ietf-pwe3-iana-allocation-12.txt… Luca Martini
- Re: [PWE3] draft-ietf-pwe3-iana-allocation-12.txt… Danny McPherson
- Re: [PWE3] draft-ietf-pwe3-iana-allocation-12.txt… Stewart Bryant
- Re: [PWE3] draft-ietf-pwe3-iana-allocation-12.txt… Luca Martini
- RE: [PWE3] draft-ietf-pwe3-iana-allocation-12.txt… Ash, Gerald R (Jerry), ALABS
- [PWE3] Re: draft-ietf-pwe3-iana-allocation-12.txt… Stewart Bryant
- RE: [PWE3] Re: draft-ietf-pwe3-iana-allocation-12… Hamid Ould-Brahim