RE: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>

Ron Bonica <rbonica@juniper.net> Thu, 23 May 2019 00:25 UTC

Return-Path: <rbonica@juniper.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21CB91200E0 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2019 17:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level:
X-Spam-Status: No, score=-2.711 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_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 5Fu0nDW_12eO for <ipv6@ietfa.amsl.com>; Wed, 22 May 2019 17:25:23 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 D812712004A for <ipv6@ietf.org>; Wed, 22 May 2019 17:25:22 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x4N0O0Dl021474; Wed, 22 May 2019 17:25:19 -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-transfer-encoding : mime-version; s=PPS1017; bh=xurdiF7Q6i0THutpYB/o+0PWX+5W83z1ZWKBOvfoDSA=; b=kLtf+eWuRtQXz1LZH95R9DjXAdCk2NuWUbF5LdsxoObo9QGp//V5Tg4rryQtnloOgWv5 ibSslZqc0TSC1OVmIjDmpd9D2FsGWlteOUYIBedx3O814N2n0W0bOdz+kp2IqWSABWLo q3d7rIPzd8e7QG80lP+PevY4c31VTQt/NPNbcxyk9iSZLMLh2ThsdJ/A4viCA8dUVnxl zod6/314/2grlQgzXQmGrwVCrR+n0xju4NeC5ptQQVQ56NXhZwNnPzS9Es212KU8W3WR RS1yKxMtYcgXZTjG9txKMfVmBgPs2f6sl1G9+EbRCSxFKG/OhXEHK1aCPBTWu9wteFVR lg==
Received: from nam04-sn1-obe.outbound.protection.outlook.com (mail-sn1nam04lp2055.outbound.protection.outlook.com [104.47.44.55]) by mx0a-00273201.pphosted.com with ESMTP id 2sng27824m-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 22 May 2019 17:25:19 -0700
Received: from BYAPR05MB4245.namprd05.prod.outlook.com (20.176.252.26) by BYAPR05MB6471.namprd05.prod.outlook.com (20.178.233.84) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.13; Thu, 23 May 2019 00:25:17 +0000
Received: from BYAPR05MB4245.namprd05.prod.outlook.com ([fe80::e1e7:cf02:f236:ab29]) by BYAPR05MB4245.namprd05.prod.outlook.com ([fe80::e1e7:cf02:f236:ab29%7]) with mapi id 15.20.1922.016; Thu, 23 May 2019 00:25:17 +0000
From: Ron Bonica <rbonica@juniper.net>
To: Bob Hinden <bob.hinden@gmail.com>
CC: "Darren Dukes (ddukes)" <ddukes@cisco.com>, IPv6 List <ipv6@ietf.org>
Subject: RE: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>
Thread-Topic: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>
Thread-Index: AQHVEKPcu9h0FngbDUm6JiENbzKuuqZ3OmhQgAAD+ACAABtkoIAAcSwAgAAMiWA=
Content-Class:
Date: Thu, 23 May 2019 00:25:17 +0000
Message-ID: <BYAPR05MB42459DB5F93B9C3C444BAA66AE010@BYAPR05MB4245.namprd05.prod.outlook.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <588C586F-C303-418E-8D26-477C4B37CF92@gmail.com> <BYAPR05MB4245494B7E35A4F30797A084AE000@BYAPR05MB4245.namprd05.prod.outlook.com> <3ED15D0E-EFAF-4991-89B6-C55DA439C0C0@cisco.com> <BYAPR05MB42453B5AA1E9F4AA523E189CAE000@BYAPR05MB4245.namprd05.prod.outlook.com> <BD45BC11-B857-4A1D-8694-C1875BF4F845@gmail.com>
In-Reply-To: <BD45BC11-B857-4A1D-8694-C1875BF4F845@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.2.0.14
dlp-reaction: no-action
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Owner=rbonica@juniper.net; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2019-05-23T00:25:15.7811890Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=Juniper Internal; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Application=Microsoft Azure Information Protection; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Extended_MSFT_Method=Automatic; Sensitivity=Juniper Internal
x-originating-ip: [66.129.241.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6c9d0a50-d7d8-405b-4ae7-08d6df1521fc
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:BYAPR05MB6471;
x-ms-traffictypediagnostic: BYAPR05MB6471:
x-microsoft-antispam-prvs: <BYAPR05MB6471A5DCE24B9CBBEE222C88AE010@BYAPR05MB6471.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 00462943DE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(376002)(346002)(366004)(39860400002)(199004)(189003)(13464003)(3846002)(229853002)(6506007)(53546011)(6116002)(7736002)(4326008)(186003)(74316002)(53936002)(26005)(25786009)(6916009)(52536014)(102836004)(9686003)(71190400001)(68736007)(446003)(99286004)(11346002)(55016002)(305945005)(71200400001)(7696005)(76176011)(4743002)(478600001)(54906003)(14454004)(2906002)(5660300002)(76116006)(86362001)(476003)(6246003)(8936002)(81166006)(66946007)(73956011)(316002)(81156014)(6436002)(256004)(14444005)(8676002)(66066001)(66476007)(66556008)(64756008)(66446008)(486006)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB6471; H:BYAPR05MB4245.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: VfAW20cOSc41C0PWLlJ8i4NaLKHbjeaQDfX32MNqzV9gcnYnRweOOJupyu9cwih2GUfWk5on/NKMOgXTZTDW06xc1po4bQiGnNgVNyGpNVKYsw7dcHA1TxjokaSKJMgeQPmIyAgDzIwtrYZSVt1K3XqjaG2Yo60Ke1Kmm8BviZ8COW0WO/a4ztHaI7U3RwRtQB+89aSPi1isGAX0OOtQG8V3CX69L21JQx2jXj5FhrIQYr6a8MktvbLPhU/vSOdf2k/nRVCZUA8jG1Ir2qZgqAIhyWMPxLV4Jifv5EsiuoIDaJ6JBnL7n4nXAEhnqrxGEfc0DCwwAgORjQNgE2+9UMLFrBcuwDz8X0OOgK+EUH7+PN734PUzTx+bB7VN51rwlDBfTDpzM1PSv0EGk2RhGMeDvKCCoFmqsZiz30JQY6o=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 6c9d0a50-d7d8-405b-4ae7-08d6df1521fc
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2019 00:25:17.5474 (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-CrossTenant-userprincipalname: rbonica@juniper.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB6471
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-22_15:, , 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=1015 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-1905230001
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/et33s42-sA420zkljHv7BdZrXBU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2019 00:25:25 -0000

Bob,

All of the SID in draft-ietf-spring-srv6-nework-programming begin with the word "END". The following are examples:

- END
- END.X
- END.DT4

So, you are correct in saying that the word "END" doesn't do much to distinguish one SID from another. Maybe the naming convention should be:

- SID
- SID.X
- SID.DT4
- etc

As long as we are consistent throughout the network programming draft, I am OK with the change.

Also, we need a good collective noun for SIDs of all types. Neither SID nor SRv6 SID work well. If we use the word "SID", it becomes overloaded. The term "SRv6 SID" is a little too close to "SID" to prevent confusion.

                                                                                                         Ron


Juniper Internal

-----Original Message-----
From: Bob Hinden <bob.hinden@gmail.com> 
Sent: Wednesday, May 22, 2019 7:29 PM
To: Ron Bonica <rbonica@juniper.net>
Cc: Bob Hinden <bob.hinden@gmail.com>; Darren Dukes (ddukes) <ddukes@cisco.com>; IPv6 List <ipv6@ietf.org>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt> 

Ron,

> On May 22, 2019, at 1:06 PM, Ron Bonica <rbonica@juniper.net> wrote:
> 
> Darren,
> 
> We may have made life more difficult for the following reasons:

How can anything be more difficult than it already is :-)

> 
> - Customers are already talking about "The END SID”.
> - At least two other drafts refer to "The END SID".  In the future, will they refer to "the otherwise nameless SID defined in draft-ietf-6man-segment-routing-header”.  
> - The naming conventions that the chairs suggest introduces ambiguity. Does the term "SID" refer to all SIDs (END.X, END.DT4, etc.) collectively? Or does the term "SID" refer to one particular SID that is defined in draft-ietf-6man-segment-routing-header.

SID would refer to the SID defined in the SRH draft.   I note that in RFC 8402, this appears to be called SRv6 SID.  That seems to be consistent.

When we reviewed the changes in what became the -19 draft, we found the use of “END SID” confusing.  We went back to see if there were other kinds of SIDs defined (for example is there a START SID, MIDDLE SID, etc.), but there isn’t.   We thought it would be better to just say SID.   If new SIDs are later defined elsewhere they can have different names that distinguish them from the SID defined in the SRH draft.  

> If the chairs insist on changing the name of the END SID, let's at least give it a new name.

To be clear, we didn’t insist, we made a suggestion that Darren adopted:

“We think calling it “END SID” makes it harder to understand, we had to go back to see if there were other SIDs defined that would have different behavior.   Since there is only one kind of SID defined, like FIRST SID.  We wonder if it can be just called “SID” and if in the future other SIDs are defined they can be called something else, for example "FOO SID”, or "SID 2”.  This is not a showstopper, but might make the document clearer.”

Bob