Re: [mpls] Alvaro Retana's No Objection on draft-ietf-mpls-lsp-ping-relay-reply-10: (with COMMENT)

"Alvaro Retana (aretana)" <aretana@cisco.com> Wed, 30 September 2015 16:26 UTC

Return-Path: <aretana@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 234351B5F50; Wed, 30 Sep 2015 09:26:45 -0700 (PDT)
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 MjguYZspbm4w; Wed, 30 Sep 2015 09:26:44 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADE021A8748; Wed, 30 Sep 2015 09:26:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2725; q=dns/txt; s=iport; t=1443630403; x=1444840003; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=5VcGd4yDS6cyaNlsKfoGbq3lHKSQgKzRsdP78X9Wo54=; b=MIXITKM/uy6s41i/gb3+Fg3hKJWc2Oa4l1iggzM1vwLmoIrVdZqt2Uc3 pmrUPGxJlhbKd4+0f/4G6fPpr/pl+sQSk4GJBNYxEN9yVelOqvP+XopwY PcvjFMIdWrqsmds8HRLQLIdaaLO7kNXGK0Knou1Nb0Dye1hcaCq4B3DHP g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AaAgC8DAxW/49dJa1egySBQQa5SIQhAQ2HdAKBNzgUAQEBAQEBAYEKhCUBAQR5EAIBCEYyJQIEAQ0FiC7LaAEBAQEBAQEBAQEBAQEBAQEBAQEBAReGcwGEfIQrLzMHhCwBBJJGgzIBjRKBT4Q2gyOSKB8BAUKCRIE+cYgzQoEFAQEB
X-IronPort-AV: E=Sophos;i="5.17,613,1437436800"; d="scan'208";a="33395657"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-6.cisco.com with ESMTP; 30 Sep 2015 16:26:42 +0000
Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t8UGQggU017558 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 30 Sep 2015 16:26:42 GMT
Received: from xch-rcd-010.cisco.com (173.37.102.20) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 30 Sep 2015 11:26:42 -0500
Received: from xhc-rcd-x15.cisco.com (173.37.183.89) by xch-rcd-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Wed, 30 Sep 2015 11:26:42 -0500
Received: from xmb-aln-x15.cisco.com ([169.254.9.98]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0248.002; Wed, 30 Sep 2015 11:26:42 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Loa Andersson <loa@pi.nu>, The IESG <iesg@ietf.org>
Thread-Topic: Alvaro Retana's No Objection on draft-ietf-mpls-lsp-ping-relay-reply-10: (with COMMENT)
Thread-Index: AQHQ+y2shocw9CdOr0a0uhi2/UxT8Z5U38WAgABjbAA=
Date: Wed, 30 Sep 2015 16:26:41 +0000
Message-ID: <D2317557.D4758%aretana@cisco.com>
References: <20150930031111.861.10509.idtracker@ietfa.amsl.com> <560B7385.6050401@pi.nu>
In-Reply-To: <560B7385.6050401@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.37.102.14]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <CB02E62C9BF7CD4A8B27E32125E9515D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/cc3aujSBa1dptOLbznpew6-5iIw>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-mpls-lsp-ping-relay-reply@ietf.org" <draft-ietf-mpls-lsp-ping-relay-reply@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Subject: Re: [mpls] Alvaro Retana's No Objection on draft-ietf-mpls-lsp-ping-relay-reply-10: (with COMMENT)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2015 16:26:45 -0000

On 9/30/15, 12:30 AM, "Loa Andersson" <loa@pi.nu> wrote:

Hi!

Sorry that I was cryptic..

>>
>>I have some comments/questions:
>>
>>1. TBD2 is the Relay Node Address Stack TLV Type.  There seems to be some
>>confusion in the text: Section 4.2. (Receiving an Echo Request)  says
>>that the "Type of the Relay Node Address Stack TLV is chosen from the
>>range 32768 to 49161Š² giving the impression that any value can be used,
>>while 8.2. (New TLV) in the IANA Considerations says that a "suggested
>>value should be assigned² giving me the impression that the assignment is
>>just a suggestion (and somehow reinforcing the text in 4.2), but the
>>original definition in 3.2. (Relay Node Address Stack) simply says that
>>the "value should be assigned by IANA².  Assuming that you simply want an
>>assignment and that it would be what is used, please clean the text up; I
>>suggest just referring to the value as TBD2 (in 4.2 and 8.2) and
>>explicitly including the text about the assignment and the range (from
>>3.2) in 8.2.
>
>I'm not sure how to read this - it looks like you are removing the range
>information. However for LSP Ping the ranges are important. The IANA
>section should state which range the code point should come from. Here
>are the allocation policies and how TLVs from the different ranges are
>reted.

In short, the range should only matter in the IANA Considerations so that
the right assignment is made.  In the rest of the text referencing TBD2
should be enough.

Explicitly, this is what I¹m proposing:

Section 3.2:

OLD
      Type: value is TBD2.  The value should be assigned by IANA from
      32768-49161 as suggested by [RFC4379] Section 3.

NEW
      Type: value is TBD2.


Section 4.2:

OLD
   The Type of the Relay Node Address Stack TLV is chosen from the range
   32768 to 49161 so that (per section 3 of [RFC4379]) an LSR that does
   not recognize the TLV knows that the TLV is optional and can safely
   ignore it.

NEW
   The Type of the Relay Node Address Stack TLV is TBD2 so that
   (per section 3 of [RFC4379]) an LSR that does
   not recognize the TLV knows that the TLV is optional and can safely
   ignore it.


Section 8.2:

OLD
   A suggested value should be assigned from "Standards Action" range
   (32768-49161) as suggested by [RFC4379] Section 3, using the first
   free value within this range.

NEW
   A value should be assigned from "Standards Action" range
   (32768-49161) as suggested by [RFC4379] Section 3, using the first
   free value within this range.





BTW, I found a new nit:  In Section 3.3. (MTU Exceeded Return Code)
s/TBD2/TBD3

Thanks!

Alvaro.