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

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Tue, 06 January 2015 23:03 UTC

Return-Path: <rajiva@cisco.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 51D3E1A00E6; Tue, 6 Jan 2015 15:03:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 uDKkWisu6KnB; Tue, 6 Jan 2015 15:03:13 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10DF41A0053; Tue, 6 Jan 2015 15:03:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7973; q=dns/txt; s=iport; t=1420585393; x=1421794993; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=asr9MAmt6npzAIlhWm7iKNktrng/1wCfyOBPhImWC3k=; b=W8jPIKz421EKqiWaX8gcK0Lkk456hC6hge87FWf1fdORyFR1QSBffpji SARfmRLVSvroqVU3+EfTcIpgvesIXBHKUvNprfSoPq2vTjMVTJb2aY635 nOMrhaYoqQci62bb5Cc1aYr/lTKg8AM8GaflrvH5Resc+qvpLgb4XoCZ7 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ak0FAH5prFStJV2U/2dsb2JhbABcgwZSWATGNgqFcwKBDhYBAQEBAX2EDAEBAQMBAQEBawsFBwQCAQgRAwEBASQEBycLFAkIAgQBDQWIJAgNwwcBAQEBAQEBAQEBAQEBAQEBAQEBAQEXjzYXKwcGhCMBBI4lg0GFOIENMII6jWUigjKBPG+BBUB+AQEB
X-IronPort-AV: E=Sophos;i="5.07,710,1413244800"; d="scan'208";a="384827431"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-8.cisco.com with ESMTP; 06 Jan 2015 23:02:54 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t06N2rid001551 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 6 Jan 2015 23:02:54 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.6]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Tue, 6 Jan 2015 17:02:53 -0600
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@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/m6uliIBH9faEWPZUJhwqq2TZyJQy9AgCq3X4A=
Date: Tue, 6 Jan 2015 23:02:53 +0000
Message-ID: <D0D1B861.243717%rajiva@cisco.com>
References: <20141204193700.25973.18733.idtracker@ietfa.amsl.com> <4A79394211F1AF4EB57D998426C9340D947C1FD1@US70UWXCHMBA04.zam.alcatel-lucent.com>
In-Reply-To: <4A79394211F1AF4EB57D998426C9340D947C1FD1@US70UWXCHMBA04.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [10.150.45.119]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <C65DD19ED60F484193A608DF9F3BD3F7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iY5SdHjXJGPUc5_eAWllOLYLyrE
X-Mailman-Approved-At: Wed, 07 Jan 2015 08:18:46 -0800
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: Tue, 06 Jan 2015 23:03:18 -0000

Hi Mustapha, 

> Having said that, I want to keep the spirit of cooperation and make sure
>we get this
> draft published. To that effect, I am not opposed to its publication as
>long as the
> following points are clarified in the draft since now FEC capability of
>the LSR peer is
> determined by a check a both adjacency and session levels:

Thanks for pointing out the below scenarios. We think that all but one are
either covered or require editorial changes.
  

1. This scenario (sending hellos with DS capability on fewer interfaces
for a peer) does NOT look realistic, since hitless upgrading a router
would result in sending v4+v6 hellos either with DS capability or without
DS capability (for a DS peer, assuming the peer was enabled for DS LDP,
default or not, in an implementation).

Perhaps, you had a different scenario in mind.


2. Yes. This scenario is well covered in section 6.1.1 point#3.


//
     3. If "Dual-stack capability" TLV is NOT present, and

Š
             resulting in any established LDPoIPv4 session being reset
             and a fatal Notification message being sent (with status

Š

//

	
3. Yes (to the expected behavior). This is somewhat covered in bullet #1
in section 6.1.1, but we can make it explicit by adding "or does not get
recognized² as below:


OLD:
If "Dual-stack capability" TLV is present and remote preference does not
match with the local preference,..


NEW:
If "Dual-stack capability" TLV is present and remote preference does not
match with the local preference (or does not get recognized),..


4 and 5. Yes (to the expected behavior). It is implicit in section 7.2
para 4. 

//..
 An LSR MAY further constrain the advertisement of FEC-label bindings for
a particular address family by negotiating the IP Capability...//

Are you suggesting to make it explicit?



-- 
Cheers,
Rajiv Asati
Distinguished Engineer, Cisco





-----Original Message-----
From: <Aissaoui>, Mustapha Aissaoui <mustapha.aissaoui@alcatel-lucent.com>
Date: Tuesday, December 16, 2014 at 12:21 PM
To: IETF Discussion <ietf@ietf.org>rg>, IETF-Announce <ietf-announce@ietf.org>
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-ldp-ipv6-14.txt> (Updates
to LDP for IPv6) to Proposed Standard

>Hi Adrian and all,
>I was the one who raised the interop issues we found while testing our
>implementation of LDP IPv6 against existing and deployed implementations.
>I proposed a simple method of using the existing FEC advertisement
>capability at the session level as a way for an LSR to detect if an
>implementation support LDP IPv6 FECs and IPv6 addresses. This existing
>FEC advertisement capability at session level is defined in
>draft-ietf-mpls-ldp-ip-pw-capability-08 but with the limitation that it
>can be used only to disable support of IPv6 FECs in LDP Initialization
>Message; we proposed to generalize the method to also indicate explicit
>support for IPv6 FECs and IPv6 Addresses in LDP Initialization Message.
>This method is safe and was also used with mLDP P2MP and MP2MP FECs when
>they were introduced. The intent here is that all session level
>capabilities in LDP should follow RFC 5561 approach.
>
>There was an individual contributor which supported the proposal on the
>mailing list but the authors chose to ignore it and went with a proposal
>which overloaded the meaning of the dual-stack capability TLV. Regardless
>of the merit of either method, the discussion on the MPLS mailing list
>was not closed properly from my perspective.
>
>Now here is the concern I raised with using the dual-stack capability.
>Not only this TLV is an adjacency level feature which is has nothing to
>do with FEC capability advertisement, but it is introducing complexity in
>the implementation which now has to check dual-stack capability for
>*each* adjacency to the peer *and* the session level FEC capability to
>decide what the peer is capable of at the *session level*.
>
>Having said that, I want to keep the spirit of cooperation and make sure
>we get this draft published. To that effect, I am not opposed to its
>publication as long as the following points are clarified in the draft
>since now FEC capability of the LSR peer is determined by a check a both
>adjacency and session levels:
>
>1. The draft is missing the behavior when multiple adjacencies exist to
>the same LSR and the peer LSR advertised the dual-stack capability only
>over a subset of these Hello adjacencies.
>I assume here the peer LSR is considered to be dual-stack capable as soon
>as any of the Hello adjacencies includes the dual-stack capability. This
>would allow a hitless upgrade scenario from an older implementation to
>one which complies to this draft
>
>2. Similarly, what would be the behavior if a hello adjacency changes
>from sending the dual-stack capability to not sending it? This would be
>for example in a hitless downgrade to a version of LDP which does not
>comply to this draft.
>I assume here that the session must be bounced since the LSRs need a
>clean state to not send IPv6 addresses and IPv6 FECs.
>
>3. The document defines 2 values for the dual-stack capability TR. It
>does not mention the behavior when an unknown value is received.
>Will that be considered a fatal error?
>
>4. The draft is missing the behavior of when the peer LSR does not
>advertise the dual-stack capability in all the Hello adjacencies but it
>advertised the enabling or disabling of the IPv6 prefix FEC capability in
>the session initialization message.
>I assume here that the absence of the dual-stack capability overrides any
>session level IPv6 FEC prefix capability advertisement.
>
>5. The draft is missing the behavior of when the peer LSR does not
>advertise the dual-stack capability in all the Hello adjacencies but it
>advertised the enabling of the IPv6 prefix FEC capability in the session
>Capability message.
>I assume the same behavior as in (4) applies here.
>
>Regards,
>Mustapha.
>
>> -----Original Message-----
>> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of The IESG
>> Sent: Thursday, December 04, 2014 2:37 PM
>> To: IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: [mpls] Last Call: <draft-ietf-mpls-ldp-ipv6-14.txt> (Updates
>>to LDP for IPv6)
>> to Proposed Standard
>> 
>> 
>> The IESG has received a request from the Multiprotocol Label Switching
>>WG
>> (mpls) to consider the following document:
>> - 'Updates to LDP for IPv6'
>>   <draft-ietf-mpls-ldp-ipv6-14.txt> as Proposed Standard
>> 
>> The IESG plans to make a decision in the next few weeks, and solicits
>>final
>> comments on this action. Please send substantive comments to the
>>ietf@ietf.org
>> mailing lists by 2014-12-18. Exceptionally, comments may be sent to
>>iesg@ietf.org
>> instead. In either case, please retain the beginning of the Subject
>>line to allow
>> automated sorting.
>> 
>> Abstract
>> 
>>    The Label Distribution Protocol (LDP) specification defines
>>    procedures to exchange label bindings over either IPv4, or IPv6 or
>>    both networks. This document corrects and clarifies the LDP behavior
>>    when IPv6 network is used (with or without IPv4). This document
>>    updates RFC 5036 and RFC 6720.
>> 
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-ldp-ipv6/
>> 
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-ldp-ipv6/ballot/
>> 
>> 
>> No IPR declarations have been submitted directly on this I-D.
>> 
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
>_______________________________________________
>mpls mailing list
>mpls@ietf.org
>https://www.ietf.org/mailman/listinfo/mpls