I am also wondering if hop-by-hop options been considered for this
application? Their interpretation in the network is unabiguous and
they also have the advantage that the work with any IP protocol or
encapsulation.
IPv6 hop-by-hop options has been considered. See
Tom,
On Thu, Apr 12, 2018 at 10:17 PM, Tom Herbert wrote:
> Mickey,
>
> Looking at these ippm drafts more closely, I have a much more
> fundamental concern.
>
> In draft-brockners-ippm-ioam-geneve-00 for instance, there is the text
> in the introduction:
>
> "In-situ OAM
On Fri, Apr 13, 2018 at 11:22 AM, Mickey Spiegel
wrote:
> Tom,
>
> On Thu, Apr 12, 2018 at 10:17 PM, Tom Herbert wrote:
>>
>> Mickey,
>>
>> Looking at these ippm drafts more closely, I have a much more
>> fundamental concern.
>>
>> In
Tom,
the term "overhead" here refers to the number of extra bytes used in the parent
protocol to carry IOAM data. IOAM data itself is of course not counted for the
comparison, because it would need to be carried in both cases.
Using your Geneve reference as an example, in order to carry IOAM
Hi,
It said in draft-brockners-ippm-ioam-vxlan-gpe-00:
" [I-D.ietf-nvo3-vxlan-gpe] defines an "O bit" for OAM packets. Per
[I-D.ietf-nvo3-vxlan-gpe] the O bit indicates that the packet
contains an OAM message instead of data payload. Packets that carry
IOAM data fields in addition to
Hi Xiaohu,
please see inline (“...FB“)
From: nvo3 On Behalf Of ???(??)
Sent: Freitag, 13. April 2018 09:42
To: Int-area ; Frank Brockners (fbrockne)
Cc: NVO3 ; int-area ; Service Function