Re: Feedback on the use of Hop-by-Hop options extension header (draft-francois-dots-ipv6-signal-option-01)

Jérôme,

I can't do better than what we wrote in RFC7045:

2.2.  Hop-by-Hop Options

   The IPv6 Hop-by-Hop Options header SHOULD be processed by
   intermediate forwarding nodes as described in [RFC2460].  However, it
   is to be expected that high-performance routers will either ignore it
   or assign packets containing it to a slow processing path.  Designers
   planning to use a hop-by-hop option need to be aware of this likely
   behaviour.

   As a reminder, in RFC 2460, it is stated that the Hop-by-Hop Options
   header, if present, must be first.

If the HbH option type is 'may change en-route', you can rewrite its
contents, but you can't change its length. And as you have understood,
most people believe that RFC 2460 says you must not insert one.

Regards
   Brian

On 08/02/2017 22:17, Jérôme François wrote:
> Dear all,
> 
> We are working on a DOTS draft about using the Hop-by-Hop option header
> to encapsulated DDoS signaling  within network to enabel a kind of
> epidemic propagation
> (https://tools.ietf.org/html/draft-francois-dots-ipv6-signal-option-01)
> 
> Some comments have been raised considering the real use of the
> Hop-by-Hop option. We would like to ask you your feedback about using it
> for very specific signaling among trusted parties. In particular, do you
> know any reference to a particular use of Hop-by-Hop in a real case.
> 
> We have also followed the mailing list discussion about header insertion,
> which obviously concerns our approach since we are extracting and inserting
> some info in headers on the paths. Even if this is is limited to specific 
> routers in a single domain, we understand that it can create problems and
> should maybe use packet encapsulation.
> 
> Best regards,
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> .
> 