I have updated draft-gray-sampled-streaming based on the numerous bits of 
feedback I have received to date.  Thanks all for the comments.  

-02 includes updates to the Client subscription sequence to make it clearer 
when different sides do different actions, adds a 'proposals' step that allows 
more error reporting and multiple options to be handed back, many 
clarifications about what role this draft is targeting, more use case examples, 
multiple YANG cleanups, numerous small changes and updates, and adding LJ 
Wobker as an author.

Please feel free to take a look, and we are always interested in getting 
feedback.  I've asked the opsawg chairs for time at IETF 106 to present, as 
well.

Thanks.

A new version of I-D, draft-gray-sampled-streaming-02.txt
has been successfully submitted by Andrew Gray and posted to the
IETF repository.

Name:           draft-gray-sampled-streaming
Revision:       02
Title:          Sampled Traffic Streaming
Document date:  2019-11-04
Group:          Individual Submission
Pages:          36
URL:            
https://www.ietf.org/internet-drafts/draft-gray-sampled-streaming-02.txt
Status:         https://datatracker.ietf.org/doc/draft-gray-sampled-streaming/
Htmlized:       https://tools.ietf.org/html/draft-gray-sampled-streaming-02
Htmlized:       
https://datatracker.ietf.org/doc/html/draft-gray-sampled-streaming
Diff:           
https://www.ietf.org/rfcdiff?url2=draft-gray-sampled-streaming-02

Abstract:
   This document standardizes both 1) a means of requesting a stream of
   packet samples from any device generating, routing, or forwarding
   traffic, and 2) receiving metadata information from the network
   element about these packet samples, and the structure of said stream
   metadata.  A main design requirement is to provide network elements
   with widely varying capabilities (e.g., ASICs, NPUs, NICs, vSwitches,
   CPUs) a mechanism to sample and export packets at high rates, by
   allowing communication of the specific bit formats of internal data
   headers applied to the packet flow, in a way that enhances
   interoperability between traffic sources and sinks.  Historically,
   Netflow and similar mechanisms have been used for these use cases;
   however, the increasing packet rates of very high-speed devices and
   increasing variance in the information available to data planes lends
   itself to both a less-prescriptive set of packet formats as well as a
   decoupling of the sampling action from the collection and analysis
   mechanisms.


E-MAIL CONFIDENTIALITY NOTICE: 
The contents of this e-mail message and any attachments are intended solely for 
the addressee(s) and may contain confidential and/or legally privileged 
information. If you are not the intended recipient of this message or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message and any attachments. If you are 
not the intended recipient, you are notified that any use, dissemination, 
distribution, copying, or storage of this message or any attachment is strictly 
prohibited.
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to