Re: [manet] I-D Action: draft-ietf-manet-dlep-da-credit-extension-04.txt

[Rick Taylor <[e-mail]>]

Hi Lou,

I'm starting to receive quite a few enquiries from industry for DLEP support for modem systems where different traffic classes flow via different paths to destinations, so called 'hub-assist' modems.  For these types of modem (an others) the ability to describe the metrics per-flow to a destination is required.

As I've mentioned before, I think there is benefit in splitting out the concept of Traffic Class Ids (as specified in this draft) into its own draft, including both the DSCP and Ethernet TOS examples, and then referring to that draft from this one, and also from others including 'metrics per TCID'. 

I'm in London, and do think this is a useful topic of conversation for the meeting/future work.  

@chairs: Would you like Lou or I to grab 10 mins at the mic to talk about this, or try to work it out offline?

Cheers,

Rick

> -----Original Message-----
> From: manet [mailto:[e-mail]] On Behalf Of Lou Berger
> Sent: 02 March 2018 22:47
> To: [e-mail]
> Subject: Re: [manet] I-D Action: draft-ietf-manet-dlep-da-credit-extension-
> 04.txt
> 
> Hi,
> 
> There are a few items outstanding on the credit draft:
> 
> I received an offline comment that I think should be noted in the draft.  The
> comment was that it might not be obvious that since queues/credit windows
> can be shared among (disjoint) sets of endpoints, that sending to one
> destination in a set reduces the available capacity to other destinations.  I'll
> propose some text on this shortly.
> 
> There are also two questions that are still open:
> 
> (A) does the WG want to keep the document as is or break apart the current
> document into two documents?
> 
> - the first being the credit window and generic traffic classification definition
> and the second being the DA/DSCP extension and traffic classification sub-DI
> 
> I can't speak for my co-authors, but I'm okay proceeding either way, but now
> is the time to decide.
> 
> (B) finally, does the WG want to take the notional Ethernet/PCP based traffic
> classification which was added as an appendix, see [1], to sanity check the
> current functional decomposition and make it a full blown Ethernet/PCP
> extension
> 
> my personal preference is to do this, it's not much effort and seems
> worthwhile.
> 
> any thoughts and/or comments would be appreciated.
> 
> I also look forward to discussing this in London (in the joint meeting with
> ccamp).
> 
> Lou
> 
> [1]
> https://tools.ietf.org/html/draft-ietf-manet-dlep-da-credit-extension-
> 04#appendix-B
> 
> 
> On 3/1/2018 6:03 PM, Lou Berger wrote:
> > Hi,
> >
> > This version completes the updates discussed at the last IETF. The
> > notable changes are:
> >
> > - Separate credit control from traffic classification
> >
> > - Ensure traffic classification is extendable to other flow
> > identification methods
> >
> >       - This included definition of a Notional Ethernet Credit Window
> > Traffic Classification (in an appendix) as a sanity check on separation
> > of mechanisms.  This can be removed at some point or moved to it's own
> > document/extension.
> >
> > - Add a management considerations section
> >
> > - other minor corrections/fixes.
> >
> > - One note, Traffic Class. Identifier (TID) was not changed as discussed
> > at IETF 100
> >
> > Lou
> >
> > On 3/1/2018 4:45 PM, [e-mail] wrote:
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >> This draft is a work item of the Mobile Ad-hoc Networks WG of the IETF.
> >>
> >>           Title           : DLEP DiffServ Aware Credit Window Extension
> >>           Authors         : Bow-Nan Cheng
> >>                             David Wiggins
> >>                             Lou Berger
> >> 	Filename        : draft-ietf-manet-dlep-da-credit-extension-04.txt
> >> 	Pages           : 26
> >> 	Date            : 2018-03-01
> >>
> >> Abstract:
> >>      This document defines an extension to the DLEP protocol that enables
> >>      a DiffServ aware credit-window scheme for destination-specific and
> >>      shared flow control.  The extension is logically composed of two
> >>      mechanisms.  The first provides credit window control, the second
> >>      identifies how flows are identified and mapped to a credit window.
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-da-credit-
> extension/
> >>
> >> There are also htmlized versions available at:
> >> https://tools.ietf.org/html/draft-ietf-manet-dlep-da-credit-extension-04
> >> https://datatracker.ietf.org/doc/html/draft-ietf-manet-dlep-da-credit-
> extension-04
> >>
> >> A diff from the previous version is available at:
> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-dlep-da-credit-
> extension-04
> >>
> >>
> >> Please note that it may take a couple of minutes from the time of
> submission
> >> until the htmlized version and diff are available at tools.ietf.org.
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >> _______________________________________________
> >> manet mailing list
> >> [e-mail]
> >> https://www.ietf.org/mailman/listinfo/manet
> >>
> > _______________________________________________
> > manet mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/manet
> 
> _______________________________________________
> manet mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/manet