Re: [babel] I-D Action: draft-ietf-babel-v4viav6-00.txt

On the topic of the ICMP IPv4 source address, I agree with Juliusz.
The specific value of that field is not required for interop, so in the
spirit of Babel specs we shouldn't over-constrain implementations.
Saying that routers need to be able to send ICMPv4 seems like the
right choice here. I would suggest adding some implementation
advice saying that using the same address (e.g. the dummy address
<https://datatracker.ietf.org/doc/html/rfc7600#section-4.8>)
on all routers is simplest but using different addresses can simplify
debugging.

On the topic of standards/experimental, I think that this specification
matches the maturity required of a proposed standard as defined in
RFC 2026 Section 4.1.1
<https://datatracker.ietf.org/doc/html/rfc2026#section-4.1.1>. When RFC 1883
<https://datatracker.ietf.org/doc/html/rfc1883> was published in 1995,
I don't think that IPv6 had a lot of implementation and deployment
experience. But I don't feel too strongly here, as the consumers of
RFCs generally don't look at the track/category when deciding what
or how to implement.

David

On Thu, Apr 8, 2021 at 7:22 AM Toke Høiland-Jørgensen <toke=
40toke.dk@dmarc.ietf.org> wrote:

> Juliusz Chroboczek <jch@irif.fr> writes:
>
> >> There is one other question in my mind. Does this draft really need to
> >> be Experimental? I would be inclined to target it to Proposed Standard.
> >
> > I'm a little uneasy on this subject.  My personal feeling is that we
> > haven't done our homework on this extension (admittedly my fault), and
> > that we don't have enough implementation and deployment experience to
> > propose it as a standard right now.
> >
> > I'd be delighted if people could disagree.
>
> Isn't that just a matter of time? I.e., we could adopt it as PS, with
> the expectation that by the time it gets published we will have built
> that experience? Or does there even need to be a final decision about
> the status at adoption time?
>
> -Toke
>
> _______________________________________________
> babel mailing list
> babel@ietf.org
> https://www.ietf.org/mailman/listinfo/babel
>