RE: Opsdir early review of draft-ietf-idr-bgp-ls-segment-routing-ext-06

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Wed, 16 May 2018 04:26 UTC

Return-Path: <ketant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1D5D127978; Tue, 15 May 2018 21:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.611
X-Spam-Level:
X-Spam-Status: No, score=-12.611 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 R9ChSY3Diglb; Tue, 15 May 2018 21:26:43 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB065127873; Tue, 15 May 2018 21:26:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3532; q=dns/txt; s=iport; t=1526444803; x=1527654403; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=DX2+Cu1FN4LY4owroh14QmFtxgDNvFyHWTMWocIH57Y=; b=IhcnmtB8uR+Jqzafc3ACXvPl++64CyBUlr8S90qtlSJAkLZ9Ve3utwVZ ST/tE1QqEkTD0nbM97K6EARX9Lsp0hYs+96CqmWt+wZFAum6QEMm78+Rk k/VWarmMLg02Rv7qXdTzhfi+q9BVO0xya3rx5mooAUHp9RFn1ySTeZgJT U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CuAACHsvta/4cNJK1cGQEBAQEBAQEBAQEBAQcBAQEBAYMUL2F8KAqDaogEjHSBeYEPkzKBeAslhEcCGoJ+ITQYAQIBAQEBAQECbBwMhSgBAQEBAgEjETMSBQcEAgEIEQQBAQMCJgICAjAVCAgCBAENBQiDHYF3CA+sBYIciEqCIgWBCYccgVQ/gQ6DDYMRAgMBgTwBATUPglqCVAKYOwkChWaIY4x7iVmGaQIREwGBJAEcOIFScBWCfosQhT5vjHGBH4EYAQE
X-IronPort-AV: E=Sophos;i="5.49,404,1520899200"; d="scan'208";a="115135730"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 May 2018 04:26:42 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w4G4Qgap007030 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 16 May 2018 04:26:42 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 15 May 2018 23:26:41 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1320.000; Tue, 15 May 2018 23:26:41 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Joel Jaeggli <joelja@bogus.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "idr@ietf.org" <idr@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-idr-bgp-ls-segment-routing-ext.all@ietf.org" <draft-ietf-idr-bgp-ls-segment-routing-ext.all@ietf.org>
Subject: RE: Opsdir early review of draft-ietf-idr-bgp-ls-segment-routing-ext-06
Thread-Topic: Opsdir early review of draft-ietf-idr-bgp-ls-segment-routing-ext-06
Thread-Index: AQHT52FX+wOvrYGWJEmMz8naprD+76QnJMZAgACmP4CACgIiUA==
Date: Wed, 16 May 2018 04:26:41 +0000
Message-ID: <22646f1db3b14b38a9b03f61adc99c49@XCH-ALN-008.cisco.com>
References: <152584833398.2904.14504730626460815575@ietfa.amsl.com> <0264f5a703b145dc9b473f0d4d96efb7@XCH-ALN-008.cisco.com> <aca9d08b3bed46a7a169b3531d10695d@XCH-ALN-001.cisco.com>
In-Reply-To: <aca9d08b3bed46a7a169b3531d10695d@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.32.181]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MIwrnZ8uoXYK6dDdoYubkS-vzws>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 16 May 2018 04:26:45 -0000

Hi Joel,

A new version 07 of this draft has been just posted to address the comments from your review as discussed in the mail thread below.

https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-segment-routing-ext/ 

Thanks,
Ketan

-----Original Message-----
From: Les Ginsberg (ginsberg) 
Sent: 09 May 2018 20:06
To: Ketan Talaulikar (ketant) <ketant@cisco.com>; Joel Jaeggli <joelja@bogus.com>; ops-dir@ietf.org
Cc: idr@ietf.org; ietf@ietf.org; draft-ietf-idr-bgp-ls-segment-routing-ext.all@ietf.org
Subject: RE: Opsdir early review of draft-ietf-idr-bgp-ls-segment-routing-ext-06

> 2.3.3.  Source Router Identifier (Source Router-ID) TLV
> 
>    The Source Router-ID TLV contains the IPv4 or IPv6 Router-ID of the
>    originator of the Prefix.  For IS-IS protocol this is as defined in
>    [RFC7794].  The Source Router-ID TLV may be used to carry the OSPF
>    Router-ID of the prefix originator.
> 
>    The Source Router-ID TLV has the following format:
> 
>     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             |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    //                  IPv4/IPv6 Address (Router-ID)              //
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>    where:
> 
>       Type: TBD, see Section 4.
> 
>       Length: 4 or 16.
> 
>       IPv4/IPv6 Address: 4 octet IPv4 address or 16 octet IPv6 address.
> 
>    The semantic of the Source Router-ID TLV is defined in [RFC7794].
> 
> * While RFC7794 Router-IDs are in fact IP addresses. OSPF Router-IDs 
> are not even if they happen to look like them, this is particularly 
> germain with ospfv3 but it’s worth making the distinction.
> [KT] Agree. I would say "The semantic of the Source Router-ID TLV for 
> ISIS is defined in [RFC7794]. For OSPF, the TLV carries the OSPF 
> Router-ID of the originator of the prefix."

[Les:] Joel - your statement is technically correct - but Ketan's suggested text revision is repeating text that is present in the first paragraph of the section.

Since the point being made is in regards to the semantics of the value field would this be more clearly dealt with by  replacing

//                  IPv4/IPv6 Address (Router-ID)              //

With 

//       4 or 16 octet Router-ID     //

??

   Les