Re: [IPv6] Apology

Ron, Jeremy,

Gorry and I concluded a long while back that deprecating Router Alert was a separate topic and should be handled in a document focused on that.

Bob

> On Mar 22, 2024, at 1:45 AM, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org> wrote:
> 
> Hi Jeremy,
> 
> Inline.......
> 
>                    Ron
> 
> 
> Juniper Business Use Only
> 
> From: Jeremy Duncan <jduncan@tachyondynamics.com <mailto:jduncan@tachyondynamics.com>>
> Sent: Thursday, March 21, 2024 11:32 AM
> To: Ron Bonica <rbonica@juniper.net <mailto:rbonica@juniper.net>>; 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>
> Subject: RE: Apology
>  
> [External Email. Be cautious of content]
> 
> Ron-
>  
> I was going to ask you a few things about this one:
>  
> draft-ietf-6man-hbh-processing-14 already has a deprecation discussion for Router Alert in 5.2.1 – should this be the place we say to deprecate it and merge into this one?
> 
> [RB] I wouldn't be averse to that. However, that decision is up to the authors of draft-ietf-6man-hbh-processing.
> 
> Are there any indications this will have MLDv2 ICMPv6 type 143 implications given the requirements for MLDv2?
> 
> [RB] The draft says that existing protocols can continue to use the Router Alert. Moreover, new versions of existing protocols (e.g.,MLDv3) can also use the Router Alert. So, there would be no implications for MLD.
> 
>                                                                                       Ron
> 
>  
> “(The Router Alert option
>    is necessary to cause routers to examine MLDv2 messages sent to IPv6
>    multicast addresses in which the routers themselves have no
>    interest.)  MLDv2 Reports can be sent with the source address set to
>    the unspecified address [RFC3513 <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/rfc3513__;!!NEt6yMaO-gk!Ete2Qh76nPjG8Leo7L5ckaU9ve1dbAWy7ZlUAko4L48x42B9OTtJnNOlzyMni4EllVWhckF9O0qo8hB_nS-8sZ6h$>], if a valid link-local IPv6 source
>    address has not been acquired yet for the sending interface.  (See
>    section 5.2.13 <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/rfc3810*section-5.2.13__;Iw!!NEt6yMaO-gk!Ete2Qh76nPjG8Leo7L5ckaU9ve1dbAWy7ZlUAko4L48x42B9OTtJnNOlzyMni4EllVWhckF9O0qo8hB_nUkZoL23$>. for details.)
> ”
>  
>  
> -Jeremy
>  
> 
> Juniper Business Use Only
> 
> From: ipv6 <ipv6-bounces@ietf.org <mailto:ipv6-bounces@ietf.org>> On Behalf Of Ron Bonica
> Sent: Thursday, March 21, 2024 11:05 AM
> To: 6man@ietf.org <mailto:6man@ietf.org>
> Subject: [IPv6] Apology
>  
> Folks,
>  
> I was scheduled to present draft-bonica-deprecate-router-alert at last night's meeting. Sadly, I am incapable of converting time zones and convinced myself that the meeting was 24 hours later than its scheduled time.
>  
> I apologize for wasting your time.
>  
> However, I do encourage you to read and comment on the draft.
>  
> Again, I apologize for wasting your time.
>  
>                                                                  Ron
>  
>  
> Juniper Business Use Only
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org <mailto:ipv6@ietf.org>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------