Re: [nvo3] BIER OAM (was: IETF101 NVO3 draft minutes posted)

[Nagendra Kumar Nainar (naikumar)]

Hi Dale,

Thanks for the catch. I just started working on updating the draft. I will 
include it in the next version.

Regards,
Nagendra

From: Greg Mirsky 
Date: Sunday, April 8, 2018 at 5:53 PM
To: "Dale R. Worley" 
Cc: NVO3 , "draft-ietf-bier-p...@ietf.org" 
, BIER WG 
Subject: Re: [nvo3] BIER OAM (was: IETF101 NVO3 draft minutes posted)
Resent-From: 
Resent-To: Nagendra Kumar Nainar , , 
, , , 

Resent-Date: Sunday, April 8, 2018 at 5:53 PM

Hi Dale,
great catch, thank you. Will correct to match the size of the Proto field, 6 
bits-long, as defined in RFC 8296 in the next update of our draft.

Regards,
Greg

On Fri, Apr 6, 2018 at 7:52 PM, Dale R. Worley 
mailto:wor...@ariadne.com>> wrote:
Greg Mirsky mailto:gregimir...@gmail.com>> writes:
> you may be surprised to check BIER OAM, section 3.1 of draft-ietf-bier-ping
> <https://tools.ietf.org/html/draft-ietf-bier-ping-03> to be precise, as it
> defines the header for active BIER OAM.

Interesting.  But I note that in RFC 8296, the next protocol field
("Proto") is 6 bits, and the "BIER Next Protocol Identifiers" is defined
to match.  But in draft-ietf-bier-ping-03, the "Proto" field is only 4
bits, although it seems to intend that the values be taken fromn "BIER
Next Protocol Identifiers".

Dale

___
nvo3 mailing list
nvo3@ietf.org<mailto:nvo3@ietf.org>
https://www.ietf.org/mailman/listinfo/nvo3

___
nvo3 mailing list
nvo3@ietf.org
https://www.ietf.org/mailman/listinfo/nvo3

Re: [nvo3] BIER OAM (was: IETF101 NVO3 draft minutes posted)

[Greg Mirsky]

Hi Dale,
great catch, thank you. Will correct to match the size of the Proto field,
6 bits-long, as defined in RFC 8296 in the next update of our draft.

Regards,
Greg

On Fri, Apr 6, 2018 at 7:52 PM, Dale R. Worley  wrote:

> Greg Mirsky  writes:
> > you may be surprised to check BIER OAM, section 3.1 of
> draft-ietf-bier-ping
> >  to be precise, as
> it
> > defines the header for active BIER OAM.
>
> Interesting.  But I note that in RFC 8296, the next protocol field
> ("Proto") is 6 bits, and the "BIER Next Protocol Identifiers" is defined
> to match.  But in draft-ietf-bier-ping-03, the "Proto" field is only 4
> bits, although it seems to intend that the values be taken fromn "BIER
> Next Protocol Identifiers".
>
> Dale
>
> ___
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>
___
nvo3 mailing list
nvo3@ietf.org
https://www.ietf.org/mailman/listinfo/nvo3