Re: [Idr] Martin Vigoureux's No Objection on draft-ietf-idr-bgpls-segment-routing-epe-18: (with COMMENT)

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 16 May 2019 09:09 UTC

Return-Path: <ketant@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF98712023D; Thu, 16 May 2019 02:09:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, URIBL_BLOCKED=0.001, 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 header.b=LHLRywFy; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=xbvrxYME
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 MDzzKml4Bqiu; Thu, 16 May 2019 02:09:40 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CE961202D0; Thu, 16 May 2019 02:09:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2648; q=dns/txt; s=iport; t=1557997780; x=1559207380; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=c5RaCkjXSESXXiqLy4MJxhLjAPcUti3TBPA/KN4orhY=; b=LHLRywFybuO7oP/zD4up5lB5zahsQKkmty+9N1ET8yXKg75iLrQcrZ+c jL6PPR2TitBYF3D/9tkgRqzKv5w5z0CodtYAsBclwRLltEWa4f5Y3vgvr SS6HGM1LXijvrLjlx3kqE/PWuhmuIo6m8RNHjeAgQw/BWk1WTa80VYU6N 0=;
IronPort-PHdr: 9a23:Lfw6eB9rrB2Crv9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+/bR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVc2IFUT9MNbhbjcxG4JJU1o2t3w=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BuAACgJ91c/4QNJK1kGwEBAgMBAQgDAQGBVQMBAQwBgT0kLANpVSAECygKhAeDRwOOc4JXfohBjWaBQoEQA1QJAQEBDAEBJQgCAQGEQAIXghQjNwYOAQMBAQQBAQIBBG0cDIVKAQEBBBIREQwBATcBCwQCAQgRBAEBAwImAgICHxEVCAgCBAENBQgagwGBagMdAQIMoA4CgTWIX3GBL4J5AQEFgTYCDkGCfg0Lgg8DBoELKAGLTheBQD+BEUaCFzU+ghpHAQEBAgGBKgESASGDCDKCJoslgg8smR4mOQkCggmGIYhnBINtghSGTI0OjDSGWIFPjGMCBAIEBQIOAQEFgWUiKT1YEQhwFYMnghsXFIM4hRSFP3IBgSiNA4EiAYEgAQE
X-IronPort-AV: E=Sophos;i="5.60,476,1549929600"; d="scan'208";a="274083244"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 16 May 2019 09:09:39 +0000
Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x4G99cQ7007024 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 16 May 2019 09:09:39 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 16 May 2019 04:09:38 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 16 May 2019 04:09:37 -0500
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 16 May 2019 05:09:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=c5RaCkjXSESXXiqLy4MJxhLjAPcUti3TBPA/KN4orhY=; b=xbvrxYME4UuTmemL+g5pO2wNXM0rk5wxxOYCeCeRgJCg1FY3c7L7weJtz3CKaqLStvRTKcb9F1a3QFL7Ng/ykh5BvQc4u9j+B9/V4Cx4LptaIbO+Rhi3RGJM4fkaKt37xj9a9hSdZOJgWSsD0aJHgrXpohLYnuWICSX4c3UaSKQ=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB3453.namprd11.prod.outlook.com (52.135.111.208) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1900.16; Thu, 16 May 2019 09:09:36 +0000
Received: from SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::3006:a080:19fa:623e]) by SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::3006:a080:19fa:623e%6]) with mapi id 15.20.1900.010; Thu, 16 May 2019 09:09:36 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Martin Vigoureux <martin.vigoureux@nokia.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-idr-bgpls-segment-routing-epe@ietf.org" <draft-ietf-idr-bgpls-segment-routing-epe@ietf.org>, Susan Hares <shares@ndzh.com>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Martin Vigoureux's No Objection on draft-ietf-idr-bgpls-segment-routing-epe-18: (with COMMENT)
Thread-Index: AQHVC8B5vQVQM+nc702HpJzqJbM9RaZtdc8w
Date: Thu, 16 May 2019 09:09:36 +0000
Message-ID: <SN6PR11MB284518E7A9A16C735456A98EC10A0@SN6PR11MB2845.namprd11.prod.outlook.com>
References: <155799493277.19716.15836404472193017936.idtracker@ietfa.amsl.com>
In-Reply-To: <155799493277.19716.15836404472193017936.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ketant@cisco.com;
x-originating-ip: [72.163.220.13]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: dbcb5be2-7842-4248-3fe8-08d6d9de3832
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:SN6PR11MB3453;
x-ms-traffictypediagnostic: SN6PR11MB3453:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <SN6PR11MB34535DF5FACE4203D0F5D7E8C10A0@SN6PR11MB3453.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0039C6E5C5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(366004)(39860400002)(136003)(396003)(13464003)(199004)(189003)(68736007)(8936002)(7696005)(2906002)(4326008)(81156014)(8676002)(81166006)(53936002)(316002)(66476007)(110136005)(53546011)(6506007)(66066001)(256004)(14454004)(102836004)(73956011)(76116006)(76176011)(66946007)(6116002)(71190400001)(71200400001)(54906003)(3846002)(14444005)(296002)(64756008)(66556008)(99286004)(52536014)(66446008)(7736002)(5660300002)(25786009)(486006)(9686003)(476003)(186003)(74316002)(55016002)(6436002)(478600001)(26005)(6246003)(229853002)(86362001)(446003)(6306002)(966005)(33656002)(305945005)(11346002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB3453; H:SN6PR11MB2845.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: y10pFN1sOMheNGn0Mmgxmef7c8nY06Gmgrwg1PLrb/yvNcA7iF9RuzfTcoQqcfn2aHhDevSzcVjByJbQ+Lh9bQyj/DbEQWPwa2NnTrItNi7Jz/PV9TWkkgO+sUFho+jHh+6Q32iBho/pmh9/YVKMVrcOUmcV4vXqMnJRpB4E4NwAcUSC0wHVVj1Q5moThMvfFozSFD2MKPqJNUl6RlbT9VJQFi0Xz65aUPdgPRZgX3ndnoXkNIz8GDR/ZoDoxWryvWp5DwvWeg38vAasinrhQU3CFEEzXSNoT/4NGqfZaIrQ49G8JTRvMCc3SU+f6IpBT+X4ZY7Syvn+eCJDxAtNG3jN2++Bf9f8zFOp61Ug3AwPMg/LkAbpt8yr82UZ3Etw+vlrOfqrSNj/5diIyffo5VANya0he+h047lcdjKHbBk=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: dbcb5be2-7842-4248-3fe8-08d6d9de3832
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 May 2019 09:09:36.7358 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR11MB3453
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.19, xch-rcd-009.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/biyUJ5aGCqBYFrwQdUcUJNKJxuc>
Subject: Re: [Idr] Martin Vigoureux's No Objection on draft-ietf-idr-bgpls-segment-routing-epe-18: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2019 09:09:48 -0000

Hi Martin,

Thanks for your review. I've fixed the naming of the SIDs in the IANA section and a few other places where it was not consistent with the naming in RFC8402.

A v19 of the draft has just been posted which includes these changes along with others that I had pending in my buffer from Alvaro's AD review and other IESG last call reviews.

https://tools.ietf.org/html/draft-ietf-idr-bgpls-segment-routing-epe-19  

Thanks,
Ketan

-----Original Message-----
From: Martin Vigoureux via Datatracker <noreply@ietf.org> 
Sent: 16 May 2019 13:52
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-idr-bgpls-segment-routing-epe@ietf.org; Susan Hares <shares@ndzh.com>; aretana.ietf@gmail.com; idr-chairs@ietf.org; shares@ndzh.com; idr@ietf.org
Subject: Martin Vigoureux's No Objection on draft-ietf-idr-bgpls-segment-routing-epe-18: (with COMMENT)

Martin Vigoureux has entered the following ballot position for
draft-ietf-idr-bgpls-segment-routing-epe-18: No Objection

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi,

thanks for this document.
I only have a minor comment:
Throughout the document, PeerNode SID, PeerAdj SID and PeerSet SID are used but the IANA section and existing registry use Peer-Node-SID, Peer-Adj-SID, Peer-Set-SID. Although there can't be any confusion, it might be worth having a single naming.