RE: [mpls] Last Call: <draft-ietf-mpls-ldp-ipv6-14.txt> (Updates to LDP for IPv6) to Proposed Standard

"Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com> Fri, 09 January 2015 23:22 UTC

Return-Path: <mustapha.aissaoui@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 969E61A005C; Fri, 9 Jan 2015 15:22:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4XNlbK5z7s1R; Fri, 9 Jan 2015 15:22:08 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-01.alcatel-lucent.com [135.245.210.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B19F41A1ABF; Fri, 9 Jan 2015 15:22:05 -0800 (PST)
Received: from us70tusmtp2.zam.alcatel-lucent.com (unknown [135.5.2.64]) by Websense Email Security Gateway with ESMTPS id 355978AB0F0; Fri, 9 Jan 2015 23:22:01 +0000 (GMT)
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id t09NM2HV012786 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 9 Jan 2015 18:22:02 -0500
Received: from US70UWXCHMBA04.zam.alcatel-lucent.com ([169.254.12.84]) by US70UWXCHHUB01.zam.alcatel-lucent.com ([135.5.2.48]) with mapi id 14.03.0195.001; Fri, 9 Jan 2015 18:22:02 -0500
From: "Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-ldp-ipv6-14.txt> (Updates to LDP for IPv6) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-ldp-ipv6-14.txt> (Updates to LDP for IPv6) to Proposed Standard
Thread-Index: AQHQD/m6uliIBH9faEWPZUJhwqq2TZyJQy9AgCqEA0CAAZ+DAIADPvEg
Date: Fri, 9 Jan 2015 23:22:01 +0000
Message-ID: <4A79394211F1AF4EB57D998426C9340D947CA754@US70UWXCHMBA04.zam.alcatel-lucent.com>
References: <20141204193700.25973.18733.idtracker@ietfa.amsl.com> <4A79394211F1AF4EB57D998426C9340D947C1FD1@US70UWXCHMBA04.zam.alcatel-lucent.com> <4A79394211F1AF4EB57D998426C9340D947C86E5@US70UWXCHMBA04.zam.alcatel-lucent.com> <065001d02a99$70bf1c00$523d5400$@olddog.co.uk>
In-Reply-To: <065001d02a99$70bf1c00$523d5400$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4_AjHsqegnmM9ihJ4wErw8jhdjE>
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jan 2015 23:22:10 -0000

Ok thanks Adrian. Yes, we should close quickly on the remaining points.

Mustapha.

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Wednesday, January 07, 2015 11:46 AM
> To: Aissaoui, Mustapha (Mustapha); ietf@ietf.org
> Cc: mpls@ietf.org
> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-ldp-ipv6-14.txt> (Updates to LDP for
> IPv6) to Proposed Standard
> 
> Hi Mustapha,
> 
> > Can we also close on the IANA assignment for the new TLVs and
> > specifically for the Dual-Stack Capability TLV?
> >
> > I assume this will be drawn from the Common Hello Parameters range of
> > the LDP TLV Type Name Space. The next available value is 0x0409. I
> > appreciate if you
> could
> > confirm this value.
> 
> Are you asking for an early allocation of this code point?
> 
> The document has been through IETF last call and with a few edits will be ready for
> processing by the IESG. After IESG approval, the IANA will make a provisional
> allocation of a code point that will be confirmed on publication of the RFC. The
> IANA is *likely* to allocate the next available value, but not if another I-D gets there
> first :-)
> 
> Unless there is a reason for a rush, I suggest that we wait for normal process.
> Constructive discussion of the remaining issues with this draft should enable that
> to complete quickly.
> 
> Thanks,
> Adrian