RE: CRH Draft Updates - Renaming the SID

[Ron Bonica <[e-mail]>]

Mark,

You have a point. CRID is too close to CRUD. CFID sounds good.

Does anyone object?

                              Ron




Juniper Business Use Only
From: Mark Smith <[e-mail]>
Sent: Wednesday, May 27, 2020 5:27 PM
To: tom petch <[e-mail]>
Cc: Ron Bonica <[e-mail]>; 6man <[e-mail]>; Brian E Carpenter <[e-mail]>
Subject: Re: CRH Draft Updates - Renaming the SID

[External Email. Be cautious of content]


On Thu, 28 May 2020, 01:49 tom petch, <[e-mail]<mailto:[e-mail]>> wrote:
From: ipv6 <[e-mail]<mailto:[e-mail]>> on behalf of Ron Bonica <rbonica=[e-mail]<mailto:[e-mail]>>
Sent: 26 May 2020 22:24

Folks,

During the call for adoption, Brian Carpenter suggested that CRH should not use the term "SID", because SRv6 already uses it.

A agree that CRH should use another term. We considered:


  *   CRH-FIB-ID
  *   Compact Routing Segment ID (CR-SID)
  *   Compact Routing ID (CRID)
  *   Forwarding Identifier Destination Object ?? (FIDO)

Does anybody have a strong preference for one or the other?
<tp>
None of the above.  CRH-FIB-ID is too long, FIDO has been used too many times elsewhere, CR-SID invites association with other uses of SID in routing and elsewhere.
CRID is the least bad but is close to CRUD, especially in lower case.

I don't think that matters that much. I'd value acronym accuracy over the possibility of distorting it to use it for criticism.

There are two types of people who could do this distortion, those with legitimate complaints, and those being childish.

You mitigate the first by good design and engineering.

The second aren't really worth worrying too much about, because having a less distortable acronym won't stop them being childish.

I think CRID does have a small ambiguity problem, is it Compact Router Identifier or Compact Routing Identifier? Even though I know it is the latter, I'm finding I'm thinking of it as the former because I'm imagining it as identifying path hops, which I tend to imagine as physical routers.

Is there either a more abstract term we can use instead of Routing, to save confusion with Router, or a more practical and less abstract term to use to ensure it is clear it is identifying a hop or forwarding point?

CFID - Compact Forwarding Identifier?

CNID - Compact Node Identifer? (I've also discovered that hosts can process RHs apparently, so Node would match what is the RFC 8200 term for an IPv6 capable host or router)

CHID - Compact Hop Identifier?

Regards,
Mark.



CORD ?
CORID?
CORS?
CORH?
CORCH?
tom petch

                                                               Ron



Juniper Business Use Only

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[e-mail]<mailto:[e-mail]>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/ipv6__;!!NEt6yMaO-gk!V2lt3rUGsR8GR1uJLAT-mDkYogl-7ZY6if14mSa2fpCrfvv6NbLFrqsqqqwIEhwy$>
--------------------------------------------------------------------