IETF Logo Mail Archive

Re: Comments on draft-ietf-rtgwg-srv6-egress-protection

Huaimo Chen <huaimo.chen@futurewei.com> Tue, 28 July 2020 22:02 UTC

Return-Path: <huaimo.chen@futurewei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0CAE3A0BFB; Tue, 28 Jul 2020 15:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 lGSoSPalErLo; Tue, 28 Jul 2020 15:02:28 -0700 (PDT)
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2116.outbound.protection.outlook.com [40.107.244.116]) (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 51B5C3A0BAB; Tue, 28 Jul 2020 15:02:16 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iC5qyPnnfhl7Kvma8p9U24Pewwt4gWDEppTpbzymjPK2QolDy009WuLM+vyRpC8whfIO7ocZpU1Qd++E9Ycs58vZv2vGY9iHIimvgFMb3Po2zIYHAp+xnZeOFzxVAEC9Ir+QQW4+isOhi72HWlwYVlchKXLmojBkkVynN7U+bBKlWdT4NApOL4iHGE1wtvGwVTGBZoQRWV+7Vu3CiU2RNFHtv/8jFPlH6l+4sceETBsL/HJ3/G3tvOCnlc9SbNAdzb4DZbI4dvNmcpc32NyUW+PK35SPvsz9tzLcpGqyOyv3sm0k27amV5n9Kpsu6FO1dj0Dr0ybYKlMOU01BOPiCA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=r/3Mhn9drFe0l/3o9Mx9cnDNYDlkkO4bWq3I8Zro1jw=; b=RDLZy7figrQf3sW99y1wov3DhDjL9NBo4SZTCEvQDexAZ9JC7ZMYyNoA+aw1Bf2T0l59UEXYqGw+T4V+VXE+cHwlG8ZrB7udcEMbVD24k2/axxaoJTP5H9cGrlXkUuZnlwfavKKzN9cmQWIhOyNvbG8D1fSRx5fKvMop/aXhSmP3yAc3WGTpAo79c9ngtQPcJnMG9EZGmbxFdIUnOUnHCp5I0dfuq2V9hhIyhWvtDQzV76mKuMTCDbzjKbt+YAiUEQ0c7xg+3Ttw+5Fg3VLauENKAWpFpc0SLNpd19MmaOlQRjvsuoRXoNZWKk731/QbE+Xr7LLWhGQb3e7KQvkZ2A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=r/3Mhn9drFe0l/3o9Mx9cnDNYDlkkO4bWq3I8Zro1jw=; b=RzlpHItK9DXhCMADMhS8rPEU/krcHsxd6rXSPfIhA8FEWf87guopgdvD3A577jP4p9vsvIxLKVqzKitC08y7/Ww0g41DiJhDFe+RRFGubzI64YriMWJUwk6AUcVzwb0JSoMWe10jC4W8mSgOKMPc2Vx9+BlgYzgQXunOwwgYb6I=
Received: from MN2PR13MB3117.namprd13.prod.outlook.com (2603:10b6:208:13a::20) by MN2PR13MB2992.namprd13.prod.outlook.com (2603:10b6:208:152::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.9; Tue, 28 Jul 2020 22:02:14 +0000
Received: from MN2PR13MB3117.namprd13.prod.outlook.com ([fe80::bd0d:e70d:94e5:81e7]) by MN2PR13MB3117.namprd13.prod.outlook.com ([fe80::bd0d:e70d:94e5:81e7%7]) with mapi id 15.20.3239.015; Tue, 28 Jul 2020 22:02:14 +0000
From: Huaimo Chen <huaimo.chen@futurewei.com>
To: Chris Bowers <chrisbowers.ietf@gmail.com>, "draft-ietf-rtgwg-srv6-egress-protection@ietf.org" <draft-ietf-rtgwg-srv6-egress-protection@ietf.org>
CC: "rtgwg@ietf.org" <rtgwg@ietf.org>, "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>
Subject: Re: Comments on draft-ietf-rtgwg-srv6-egress-protection
Thread-Topic: Comments on draft-ietf-rtgwg-srv6-egress-protection
Thread-Index: AdZkJZSGuOKvhVWwRgyqT4wnzVQXngA8aeEAAATRaPk=
Date: Tue, 28 Jul 2020 22:02:14 +0000
Message-ID: <MN2PR13MB3117202FDDB01532F1ED3D58F2730@MN2PR13MB3117.namprd13.prod.outlook.com>
References: <MW3PR11MB4570EACEE8C80723A0411F31C1720@MW3PR11MB4570.namprd11.prod.outlook.com>, <CAHzoHbtORMa7N6o=nD+2HfPt3-2fovCeK5HvGQSdYy2WQica8w@mail.gmail.com>
In-Reply-To: <CAHzoHbtORMa7N6o=nD+2HfPt3-2fovCeK5HvGQSdYy2WQica8w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [73.114.233.24]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 39ca958e-31e1-4d85-e781-08d83341e2f8
x-ms-traffictypediagnostic: MN2PR13MB2992:
x-microsoft-antispam-prvs: <MN2PR13MB29925619069C72CC9A3319B5F2730@MN2PR13MB2992.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 5XAbK1jNSw85yGl/NCZKhonDSZ2L/XotQOwndmNVQgXfHS1tBJnu2xtb3jnWvfRGu9rRhCOdQWtLwkNgZSwvI+HB9kuq7wgD85WCJbMQonpda/DXAwf1RGWAAFVsPCXrc8RZECSeHfLHSxKytEquTTxa04IVMhwVsBxnruj62yEBe0xpspgExXr+YcOIkSd4e92oHdfvbuyFSNhHp7yVuZuTiWgCYNFKszr7wAoJGGeoAqFrFaGLIPoWQr3/DjWooNP2M6YreS4+As+HbTSKnwvQFJ5wBfAoxuXquM8UMzefP9A7Q/oPqqbYisF4ZlEr43IrTpBJrX057UF2EPpIxBmPO05T8ZYUIc2zZc34CQ11oZ2siGO92q4193ku/F2MQg3gBsrbgRZ97OnhCYN8NQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR13MB3117.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(376002)(39850400004)(396003)(136003)(366004)(346002)(53546011)(6506007)(55016002)(76116006)(52536014)(9686003)(966005)(508600001)(316002)(4326008)(44832011)(66446008)(64756008)(66556008)(91956017)(26005)(33656002)(5660300002)(8936002)(86362001)(110136005)(2906002)(66476007)(8676002)(71200400001)(54906003)(166002)(186003)(19627405001)(7696005)(66946007); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: WDNxMUNd/fxM7un49w9GE8ptcWrc6K3X2xOKl0IEorYMt4H8yxYpd0afTih36qqdyewLLDoAKM6tMTMSZs5Q1+fLoAJ0lWF3cNg0ZZq0PNMd4V7B9pLUnwiaaXdxQ3X03iO9S3U0FfrkjzwsGsLEj2pgvM0sTWwOgUNftpzupBF13ZFJQ/7q++EwAixI6auCHjDfmYkH6LOutKBHXGwJiPgDoS45PcNJm9gcOTfKrJ0SMRlARH1wjjLSvsspbyu/i+fmV/VhBKFkPS0xRfEIzI17UEuFwqtB7uG2Uuo/3k/ZhaeQ3gNG/cKzlhNAWYAdB+45EepsxjPQ8qYsJc2DePxkJTMsV0BAHW/t8I5bqG4p4h8SaPGEr4jT0NM5XkohyNDWJgxAI/GXpkSVH8os3YFowLkc+sU8w+F+L2Q/2PYbrF8IRyKc5Rhi2/C6JO/JAORa/FS7Y0OIp0KvtkKbiK0exTtswzwx+bUP58sqoY7/o2l+Vwb8JDab8eXub13kZp+/cs2GjfC9Z6Jsnf9kGqN8WG5qlIyhLTVx8oO2f2rIgdHKoz17v0OAmsVIQhxrQJLmYciAC+eLJoDkvNwSdika25xFzeLhh+6kWm/Rjsh3OrJIjewoAu1v7DB8nOy3q4FWx9YALnNFEsFR75rXtQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB3117202FDDB01532F1ED3D58F2730MN2PR13MB3117namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR13MB3117.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 39ca958e-31e1-4d85-e781-08d83341e2f8
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jul 2020 22:02:14.5529 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: LglIHyrwY9tJ7vVaA/eKcUPvfFCPI1NKcUZmZ/wS/zM/nM9FEKepYj39He8mBpcwepRnaOZhipWbaYJm+1tyig==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB2992
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/MISB6-FTvu2HalBgg0AZK9HpOoM>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2020 22:02:38 -0000

Hi Chris,

    Thank you very much for your suggestion.
    We will add the reference accordingly.

Best Regards,
Huaimo
________________________________
From: Chris Bowers <chrisbowers.ietf@gmail.com>
Sent: Tuesday, July 28, 2020 3:42 PM
To: draft-ietf-rtgwg-srv6-egress-protection@ietf.org <draft-ietf-rtgwg-srv6-egress-protection@ietf.org>
Cc: rtgwg@ietf.org <rtgwg@ietf.org>; Ketan Talaulikar (ketant) <ketant=40cisco.com@dmarc.ietf.org>
Subject: Re: Comments on draft-ietf-rtgwg-srv6-egress-protection

I would also suggest that the authors of draft-ietf-rtgwg-srv6-egress-protection add a reference to Section 5.1 of RFC8402 (Segment Routing Architecture) which describes the Mirror SID.

Thanks,
Chris


On Mon, Jul 27, 2020 at 10:18 AM Ketan Talaulikar (ketant) <ketant=40cisco.com@dmarc.ietf.org<mailto:40cisco.com@dmarc.ietf.org>> wrote:
Hello,

I am summarizing the questions/comments on the mike on the list with more details for a follow-up from the authors.

1) SRv6 Mirror SID is a new behavior for SRv6 SIDs that needs to be formally introduced, defined (using a pseudocode?) and a IANA code-point allocated for it. E.g. refer https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-16#section-4.6<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-spring-srv6-network-programming-16%23section-4.6&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C9fe1997188ce49d2dbc208d8332ebfc5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637315623167169013&sdata=EIuE1TCcJ4vfxuEI44V8BGJQ54qIKLUYcfE3Urm2Epk%3D&reserved=0> and for codepoint check https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-16#section-9.2<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-spring-srv6-network-programming-16%23section-9.2&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C9fe1997188ce49d2dbc208d8332ebfc5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637315623167179016&sdata=TdiaIKsK%2FNJ3vZKT9v%2B53u%2FOEhkho67o4A%2FdCKj2bGQ%3D&reserved=0>. My question was whether the authors intended to add that in this document or a separate Spring document (may be the chairs can guide here)? Regardless, this would be something that would require review from the Spring WG.

2) Once (1) has been addressed, then it provides the necessary foundation for the review of the IGP encodings for signaling of SRv6 Mirror SIDs (Section 4). I would suggest that this proposal then get reviewed in the LSR WG - whether in this document or as a separate LSR draft is up to the chairs.

Thanks,
Ketan

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org<mailto:rtgwg@ietf.org>
https://www.ietf.org/mailman/listinfo/rtgwg<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Frtgwg&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C9fe1997188ce49d2dbc208d8332ebfc5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637315623167179016&sdata=Rqc%2F%2BgsjPCY1og8UcRA2VyFhk2yZO3Cg3SVeouex96s%3D&reserved=0>

v2.23.0 | Report a Bug | By Email