[manet] Status of 4 DLEP extensions (was Re: Prague)

[Lou Berger <[e-mail]>]

Hi Justin/WG,

At the last meeting
(https://datatracker.ietf.org/meeting/98/proceedings#manet) we reviewed

1. draft-ietf-manet-dlep-latency-extension-00
2. draft-ietf-manet-dlep-multi-hop-extension-00
3. draft-ietf-manet-dlep-pause-extension-00
4. draft-ietf-manet-dlep-da-credit-extension-01

At the last meeting we said both 1 and 2 were ready for LC.

We did receive feedback (from Rick) at the last meeting  that it would
be good to generalize latency range communication defined in #1 to other
parametric DIs (e.g.,bps).  It's my feeling that doing so in a generic
fashion doesn't make sense as each type will require an their own
extension value, that is unless we wanted to force support for all such
DIs even though this isn't required even by base DLEP.  Given there
hasn't been any on list proposals on specific changes to the draft, and
we' wait one meeting for such, I'd like to propose that we not make any
substantive changes to the mechanisms defined in the draft at this time. 

What do you (chairs and WG) think?

We'd like to move forward and LC 1 and 2 at the chairs convenience. 

WRT 3:
At the last meeting it was agreed to update the format of the Queue
Parameter Data Item to use Rick container idea.  I've taken a pass at
this (published today) and this document is restructured format is ready
for WG discussion.  Once this issues is close, this document will also
be ready for LC.

WRT 4:
My update on this document is overdue.  I'll try to get it done before
the meeting.  The latest working text of the document will be available
in the repo [1] (but not yet) while draft submissions are closed.  I'd
be happy to discuss this in Prague with whoever is around and interested.

Lou

[1]
repo: https://github.com/louberger/dlep-extensions
formatted:
https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?url=https://raw.githubusercontent.com/louberger/dlep-extensions/master/credit/draft-ietf-manet-dlep-da-credit-extension.xml&modeAsFormat=html%2Fascii


On 7/3/2017 1:15 PM, Justin Dean wrote:
> We also need to get progress and discussion happening on this list to
> make future meetings useful and productive.