[Idr] draft-li-idr-bgp-ls-sr-policy-path-segment

Shraddha Hegde <shraddha@juniper.net> Mon, 06 May 2019 10:31 UTC

Return-Path: <shraddha@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 644FC120130; Mon, 6 May 2019 03:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level:
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 uoCkgZV7flFB; Mon, 6 May 2019 03:31:14 -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 3DB7512012A; Mon, 6 May 2019 03:31:11 -0700 (PDT)
Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x46ATtql016576; Mon, 6 May 2019 03:31:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : content-type : mime-version; s=PPS1017; bh=CAdVGQ38WSSIeqE5YQvjhYCtOpMiZhYzaLrImOrLATM=; b=L2uylOFJWdVyFe9pX+3J0zi0GWC8X7ipEDbwy+HBwMKpSuHohCH2zz8/fsqWhZNuyimd RTbFXX2l1hLiudWi1ROZceSgVtAzpHsH1vqaAA4nOkaVVS99jgnQvUV8D8JPwWIZmrTK CdUy+CRJWnUHend/twTG+FEs/WRLP3U27BxjfHCWOt6FZnz4JvgRe4qgdQ2zk4xtAamD HzpN2qfyVE/iu1wGSlnuUkANBHIz65vuG6Wd20NtPZgM+9kf7vXDZFA1swi3Fq5ygWff WxpO95euTHRcYbPEgUE/vDFLNABxaCtR8D50wycTtMBEw/oif2fdVQo4itwLQt2w7Xoj jA==
Received: from nam02-sn1-obe.outbound.protection.outlook.com (mail-sn1nam02lp2051.outbound.protection.outlook.com [104.47.36.51]) by mx0b-00273201.pphosted.com with ESMTP id 2sahue83gx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 06 May 2019 03:31:07 -0700
Received: from BYAPR05MB3943.namprd05.prod.outlook.com (52.135.195.146) by BYAPR05MB6742.namprd05.prod.outlook.com (20.177.187.31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1878.17; Mon, 6 May 2019 10:31:05 +0000
Received: from BYAPR05MB3943.namprd05.prod.outlook.com ([fe80::798f:f357:3a59:f065]) by BYAPR05MB3943.namprd05.prod.outlook.com ([fe80::798f:f357:3a59:f065%7]) with mapi id 15.20.1878.019; Mon, 6 May 2019 10:31:05 +0000
From: Shraddha Hegde <shraddha@juniper.net>
To: "draft-li-idr-bgp-ls-sr-policy-path-segment@ietf.org" <draft-li-idr-bgp-ls-sr-policy-path-segment@ietf.org>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: draft-li-idr-bgp-ls-sr-policy-path-segment
Thread-Index: AdUD8LJw2VRtfkBWRQ2Pk6e5jY9wGA==
Date: Mon, 06 May 2019 10:31:05 +0000
Message-ID: <BYAPR05MB3943C32D63B37858EEB92944D5300@BYAPR05MB3943.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.1.100.23
dlp-reaction: no-action
x-originating-ip: [116.197.184.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8eb246ad-2e19-4ada-3902-08d6d20df1d5
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(4618075)(2017052603328)(7193020); SRVR:BYAPR05MB6742;
x-ms-traffictypediagnostic: BYAPR05MB6742:
x-microsoft-antispam-prvs: <BYAPR05MB6742D6C7654CA0C620CB87A9D5300@BYAPR05MB6742.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0029F17A3F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(136003)(396003)(346002)(366004)(39860400002)(199004)(189003)(966005)(86362001)(81166006)(81156014)(8676002)(186003)(8936002)(55016002)(53936002)(6916009)(450100002)(478600001)(4326008)(14454004)(25786009)(2906002)(5640700003)(74316002)(6436002)(33656002)(316002)(9686003)(6306002)(6506007)(2501003)(71200400001)(66446008)(30864003)(71190400001)(66946007)(73956011)(26005)(6116002)(102836004)(66066001)(76116006)(68736007)(99286004)(7696005)(3846002)(5660300002)(476003)(66476007)(256004)(66556008)(64756008)(14444005)(52536014)(2351001)(7736002)(305945005)(486006); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB6742; H:BYAPR05MB3943.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: Bfn46w379ALtT10kJgmj2tXNBeNDBVqgxBrQu8+RCK8hrFcCr3oxZuFz0a48Gd+Zh3PdkYxrhjLQH0O9gObP1yOUaRbE9P90pWiZIT7Ec1LNruzYFj7fJ1qtczno1Wl+3lDkkZX5ZoaMVJDiNaWrvaQwn47k4xXXD5WNsYpA3NqKluahupO88pljV4sC4b1QyuRNdzI8tiBj7RfIUkqQ54PLnHALFzoDVu2zy8OcWAkO+2tlVxhg2oK/gsZWJ0aCo97x2SQy9CeztdBLTTySmC6KNaba5imKM4VZ9Eu9mf5WP3ZQJayhp4w4cjBkdTp4Ez3pCUORchhzDzZxYA7buZzL6x6LDrcV/EApLLF86oadu7M4Loi30mpDnjDUIrcBjwKLUEvPdWdgXVqbryDuS4GFI03vaoJhPkLR1JGnRUU=
Content-Type: multipart/alternative; boundary="_000_BYAPR05MB3943C32D63B37858EEB92944D5300BYAPR05MB3943namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 8eb246ad-2e19-4ada-3902-08d6d20df1d5
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 May 2019 10:31:05.1705 (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: BYAPR05MB6742
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-06_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=526 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905060092
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/pzoV7g3O4vpL4mnI0I-PU16_dlM>
Subject: [Idr] draft-li-idr-bgp-ls-sr-policy-path-segment
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, 06 May 2019 10:31:16 -0000

Authors,


Some comments on the draft.

1.      Section 3.1 SR Path Segment
"Also, it can be used for identifying an SR candidate path or an SR
   Policy defined in [I-D.ietf-spring-segment-routing-policy<https://tools.ietf.org/html/draft-li-idr-bgp-ls-sr-policy-path-segment-01>]."

When the path-segment is used for identifying SR policy/candidate path,
The SR Path Segment sub-TLV should appear in the SR policy as below. Pls update figure 1.

SR Policy SAFI NLRI: <Distinguisher, Policy-Color, Endpoint>
           Attributes: Tunnel Encaps Attribute (23)
           Tunnel Type: SR Policy
               Binding SID
               Preference
               Priority
               Policy Name
               Explicit NULL Label Policy (ENLP)
               Path Segment
               Bidirectioanl Path
                   Segment List
                       Weight
                       Segment
                       Segment


The Path Segment Sub-TLV may be associated with SR Policy as well as the Segment List
Simultaneously, or may be associated with SR-Policy or segment List alone based on usecases.
2.      I suggest to update the IANA section, with code points and NLRIs/attributes where the TLVs/sub-TLVs appear in BGP-LS NLRI
      Along with the code-points. It's useful for implementors as well as IANA to keep the registry up to date.

      Rgds
      Shraddha