Re: [Idr] Comments on draft-hegde-idr-bgp-ls-epe-inter-as-00

Srihari Sangli <ssangli@juniper.net> Mon, 08 April 2019 18:13 UTC

Return-Path: <ssangli@juniper.net>
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 9B70D12032C; Mon, 8 Apr 2019 11:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.339
X-Spam-Level:
X-Spam-Status: No, score=-1.339 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KHOP_DYNAMIC=1.363, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 gLveMiT9lmY4; Mon, 8 Apr 2019 11:13:16 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 3D226120326; Mon, 8 Apr 2019 11:13:12 -0700 (PDT)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x38HxigH023687; Mon, 8 Apr 2019 11:13:08 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=PasxEFACA9yKkq66MV6pi12DmL/EZzsLDHwyA12GAZQ=; b=Cvtw2BwWGniky/DeoAZy46L8VSTRK6rND6PIZ9ffCddVTEceBE2v6RWHyl0lBfs6btUu SXbmNCIGdcBaHXPOIpXreHcRrWEyDJVQQBh9KG+arGSRDTregPsnmRviIeVs9MQgLtId Q4bGi3ZJDnrTveIrWPLnsi/d8b2BEUkMcVeNvJhSGaTbVruSHU/Lx4KmFgbszigzhcKQ wDoQ+Ju6rIfsa8DO1YqaubTSsf1PAD9AzWc+EGBK3nr0EmXstTMQUTFuMHitIg+IoDuW F3B+zsniPvvHropkJG3WoS/KyiXegUA9lSdh9Vq77E4enV5iXMQU6CgVTAkWl2SqD8WL Tg==
Received: from nam03-dm3-obe.outbound.protection.outlook.com (mail-dm3nam03lp2051.outbound.protection.outlook.com [104.47.41.51]) by mx0b-00273201.pphosted.com with ESMTP id 2rr2p30vqu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 08 Apr 2019 11:13:08 -0700
Received: from BYAPR05MB4551.namprd05.prod.outlook.com (52.135.203.158) by BYAPR05MB5061.namprd05.prod.outlook.com (20.177.230.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.11; Mon, 8 Apr 2019 18:13:05 +0000
Received: from BYAPR05MB4551.namprd05.prod.outlook.com ([fe80::4a2:5267:9227:2d61]) by BYAPR05MB4551.namprd05.prod.outlook.com ([fe80::4a2:5267:9227:2d61%5]) with mapi id 15.20.1792.009; Mon, 8 Apr 2019 18:13:05 +0000
From: Srihari Sangli <ssangli@juniper.net>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, "draft-hegde-idr-bgp-ls-epe-inter-as@ietf.org" <draft-hegde-idr-bgp-ls-epe-inter-as@ietf.org>, Alvaro Retana <aretana.ietf@gmail.com>, Susan Hares <shares@ndzh.com>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Comments on draft-hegde-idr-bgp-ls-epe-inter-as-00
Thread-Index: AdTj8Oxb1mhZw8f0RP6O8MTUg8xH7gKc+LIA
Date: Mon, 8 Apr 2019 18:13:05 +0000
Message-ID: <1042EEB5-CAF2-4508-8CE8-8AE48C8310AF@juniper.net>
References: <SN6PR11MB28459697EBF5E940AC496E1AC15F0@SN6PR11MB2845.namprd11.prod.outlook.com>
In-Reply-To: <SN6PR11MB28459697EBF5E940AC496E1AC15F0@SN6PR11MB2845.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [116.197.184.10]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 70a43ce3-d22f-4b02-827b-08d6bc4dd8a4
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(4618075)(2017052603328)(7193020); SRVR:BYAPR05MB5061;
x-ms-traffictypediagnostic: BYAPR05MB5061:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BYAPR05MB5061A510F439BCF14FCFC7D0B92C0@BYAPR05MB5061.namprd05.prod.outlook.com>
x-forefront-prvs: 0001227049
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(136003)(396003)(346002)(39860400002)(189003)(199004)(486006)(110136005)(256004)(14444005)(478600001)(66066001)(305945005)(8676002)(2616005)(476003)(8936002)(82746002)(11346002)(316002)(5660300002)(6306002)(86362001)(6512007)(966005)(25786009)(99286004)(4326008)(446003)(81166006)(53936002)(81156014)(68736007)(6246003)(7736002)(33656002)(6116002)(26005)(102836004)(6486002)(186003)(2906002)(97736004)(36756003)(6436002)(106356001)(105586002)(14454004)(2501003)(71190400001)(561944003)(83716004)(71200400001)(229853002)(3846002)(76176011)(6506007); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB5061; H:BYAPR05MB4551.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: ue0vh264GyIEQVSQ/3mWutSEgK4nDkPoytmHAmsEF3Ado3xOJ3e4bZXDuMtngxzIQqVTETta7R64uvZbxMP979+oj1wencQn1m7bTx+gH+2YHxvmxZEL1s8vP5YGWQPK0zc4qnLSXP86udqbvow1kT+fTio8wQISQGNEEqJQiv1TDkM/I/zymiI5VOn+ZekgTsJn/lM5aeEvoAOTu1VGYxH7+tRFpCZ8eH7CDorKle7PaNvdKuBBIPPsWczjXWUKmSkcrWbZQsN7f/U/VI7Yb8UbE7K2IQbQ3EvCfyQe8WE9Xnphw5xWbK6JSDL7/cIDdgpgt3aML9gWUlBXP2ollCrqJDIqgC5AE+at8O77112RwJmGJmZNW6VykQehFGbFbHzPR1cHg+P91y1rXCrzX4Bn9rDn656ER4LJsDWHBjc=
Content-Type: text/plain; charset="utf-8"
Content-ID: <F0D1283525BAB74CB18FF6DD12DD5F9F@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 70a43ce3-d22f-4b02-827b-08d6bc4dd8a4
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Apr 2019 18:13:05.1046 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB5061
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-08_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904080143
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/HB5Fv6SRwdm-ix5BPqJejmTbmbQ>
Subject: Re: [Idr] Comments on draft-hegde-idr-bgp-ls-epe-inter-as-00
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: Mon, 08 Apr 2019 18:13:19 -0000

Ketan, Sue, Alvaro and others,

The comments below and the comments I received during the presentation are going to addressed in the next version of the document that will be posted shortly. We would appreciate feedback on that version.

-Srihari Sangli (on behalf of authors).
 

On 26/03/19, 10:28 PM, "Ketan Talaulikar (ketant)" <ketant@cisco.com> wrote:

    Hi Shraddha/Srihari,
    
    Some comments on this draft that was presented at IDR session on Monday.
    
    Sec 3 talks about the F flag and that it is set on the "FRR SID". I get the impression that this introduces new/additional BGP Peering SIDs called "FRR SID" to provide backup for some "normal" BGP Peering SIDs. It would help if additional text and clarification with examples were provided to indicate how this is all achieved and the proposal to advertise all these "FRR SID" and their association with the "normal" BGP Peering SIDs.
    
    The new thing being proposed in this draft in Sec 4 is about including the Local Address TLVs along with the Link NLRI that represents the BGP Peering session and carries the BGP Peer Node SID TLV so that it may be possible to map the underlying Link NLRIs that are associated with the BGP Peer Adjacency SID TLVs. I believe this aspect is useful. I would suggest to reuse TLV 259 and 261 instead of having to define new TLVs and codepoints - you would find they are exactly what you are proposing to introduce.
    
    Regarding advertisement of other details and TE attributes for Inter-AS links, I would request you to check/review https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dketant-2Didr-2Dbgp-2Dls-2Dbgp-2Donly-2Dfabric-2D02&d=DwIFAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=D2PxhI4eSYvYupK3D7veb79n9CFF8cAUYGNtuecl6W0&m=JdCQ5R68LEfi9dn9sB9RvTNCNGrGidgq5dwV-Q7PKB8&s=3X5cPR3OlogxnwfG80VPv-zeOY4ohv0kCcw0HjXxSU4&e= which covers this topic. It is applicable to any BGP-only network or part of it including the Inter-AS links.
    
    Thanks,
    Ketan