Re: [nvo3] IEEE 802.Qcn VDP for NVO3 draft available for review

2017-02-09 Thread ao . ting
Hi Pat， I will review the draft, and try to feedback. BR. Ting From: nvo3 [mailto:nvo3-boun...@ietf.org] On Behalf Of Pat Thaler Sent: Friday, January 27, 2017 12:29 AM To: nvo3@ietf.org Subject: Re: [nvo3] IEEE 802.Qcn VDP for NVO3 draft available for review We haven't received any

Re: [nvo3] Encap draft published by design team

2017-02-09 Thread Joe Touch
On 2/9/2017 12:05 PM, Tom Herbert wrote: >> Otherwise, the only way to know where the Nth TLV field starts is to >> parse through the N-1th, which - recursively - reduces to requiring >> iterative processing. >> > Yes, and iterative processing of an open ended list of TLVs is still > hard to do

Re: [nvo3] Encap draft published by design team

2017-02-09 Thread Tom Herbert
On Thu, Feb 9, 2017 at 9:03 AM, Sam Aldrin wrote: > Hello NVo3 WG, > > NVo3 Design Team for encap has put in quite a bit of effort to meet, discuss > and hashout various requirements and issues and coming up with a draft on > proposed encap. Thanks to all who have

Re: [nvo3] Encap draft published by design team

2017-02-09 Thread Tom Herbert
On Thu, Feb 9, 2017 at 11:42 AM, Joe Touch wrote: > Hi, Tom, > > > On 2/9/2017 11:33 AM, Tom Herbert wrote: >> On Thu, Feb 9, 2017 at 10:46 AM, Joe Touch wrote: >>> ... >>> >>> - the discussion of TLV vs. bitfields needs a bit more expansion. E.g., TLV >>>

Re: [nvo3] Encap draft published by design team

2017-02-09 Thread Joe Touch
Hi, Tom, On 2/9/2017 11:33 AM, Tom Herbert wrote: > On Thu, Feb 9, 2017 at 10:46 AM, Joe Touch wrote: >> ... >> >> - the discussion of TLV vs. bitfields needs a bit more expansion. E.g., TLV >> necessarily requires serial processing, whereas bitfields can be processed >> in

Re: [nvo3] Encap draft published by design team

2017-02-09 Thread Tom Herbert
On Thu, Feb 9, 2017 at 10:46 AM, Joe Touch wrote: > Hi, all, > > I found this document to have useful context for discussion for the most > part. > > Some notes below: > > - it would be useful to provide a summary of the unique requirements of NVO3 > that necessitate a new

Re: [nvo3] Encap draft published by design team

2017-02-09 Thread Joe Touch
Hi, all, I found this document to have useful context for discussion for the most part. Some notes below: - it would be useful to provide a summary of the unique requirements of NVO3 that necessitate a new encapsulation protocol - there are many encapsulation issues not addressed, e.g., MTUs,

[nvo3] Encap draft published by design team

2017-02-09 Thread Sam Aldrin
Hello NVo3 WG, NVo3 Design Team for encap has put in quite a bit of effort to meet, discuss and hashout various requirements and issues and coming up with a draft on proposed encap. Thanks to all who have participated and made it possible. This document could be found at URL: