Re: Adoption call criteria for CRH? [was: Re: CRH and RH0]

Hi John, my 2 cents.

Last week someone came to the working group and said “here is a new routing header, it carries opaque numbers that get mapped to IPv6 addresses and some other stuff.  Please adopt it.”

Now the WG is asking what this thing is, what is the author's intent, how does it fit into other work ongoing in 6MAN and other working groups.

Contrast this with every other routing header defined that has come from a WG with a plan for how it is to be used and usecases for it:
Type0 - IPNG
RPL - ROLL
Type2 - MEXT
SRH - SPRING

CRH seems out of place...

Does CRH even fit in the 6man charter?  It doesn’t appear so, it looks to me like the tip of an iceberg.
"It (6man) is not chartered to develop major changes or additions
to the IPv6 specifications.”

Darren

> On May 13, 2020, at 3:59 PM, John Scudder <jgs=40juniper.net@dmarc.ietf.org> wrote:
> 
> I’m a little confused about this conversation and I’d like to ask the chairs for clarification. My actual questions are at the end of this long(ish) message, and can be summarized as (1) does 6man require consent from SPRING before defining routing headers, and (2) what criteria are the chairs using to decide when an adoption call is OK?
> 
> It seems to me there are at least two, only vaguely related, conversations going on. One of them is a debate about the assertion that 6man can’t even consider taking up CRH unless SPRING approves it. The other is a more free-wheeling line of questioning about “what is CRH for anyway”? 
> 
> I presume both of these relate to Ron’s request for an adoption call. Here’s what the minutes from the interim have:
> 
>> Bob: Thank you Ron. I think it's too early for adoption call.
>> 
>> Ron: What is needed to get to adoption call.
>> 
>> Bob: I can't answer right now.
>> 
>> Ron: Can I ask on list?
>> 
>> Bob: OK.
>> 
>> Ole: Related to what's going on in spring.
> 
> Too bad we have no audio recording, but that’s not too far from my recollection. Anyway, I don’t think I’ve seen this answered on list yet, so I’m asking again.
> 
> Regarding the SPRING-related process stuff:
> 
> I have quite a bit of history with how SPRING was chartered; I was one of the original co-chairs and helped write the charter, god help me. I can tell you for certain there was no intent that SPRING should have exclusive ownership of source routing in the IETF, the name isn’t a power-grab, it’s a clever backronym, as we do in the IETF. If one entity in the IETF were to take charge of all source routing, that sounds more like a new area than a WG. But don’t take my word for it, go read the various iterations of the charter. As anyone who’s looked at the Segment Routing document set can tell, Segment Routing is one, very specific, way of doing source routing. As Ketan and others have pointed out, it’s a pile of architecture plus the bits and pieces to instantiate that architecture. That is fine, but the idea that merely because a technology might be used to instantiate part of that architecture, it’s owned by SPRING, is overreach. Just because a sandwich is a filling between two pieces of starch, doesn’t mean every filling between two pieces of starch is a sandwich. [1]
> 
> But at any rate, the question for the chairs is: do you think 6man needs SPRING’s permission in order to consider adopting CRH? Does 6man need permission from SPRING for all routing headers, or just some, and if it’s just some, what characterizes them?
> 
> Regarding the more general “what is CRH for anyway” stuff:
> 
> This seems to me to be exactly the kind of discussion one would normally have in the context of an adoption call. Why is it not being had in that context? To rewind back to the interim, if it’s still “too early for adoption call”, what has to happen for it not to be too early?
> 
> Thanks,
> 
> —John
> 
> [1] https://cuberule.com
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------