Re: [tcpm] New version for draft-ietf-tcpm-yang-tcp

["Scharf, Michael" <[e-mail]>]

Hi Med,

Thanks. I have noted that comment and suggest to fix it in -08.

Michael

> -----Original Message-----
> From: [e-mail]
> <[e-mail]>
> Sent: Friday, June 17, 2022 3:14 PM
> To: Scharf, Michael <[e-mail]>; [e-mail]
> Cc: [e-mail]
> Subject: RE: New version for draft-ietf-tcpm-yang-tcp
> 
> Hi Michael,
> 
> I have one minor comment:
> 
> OLD:
>               The value
>               should be unknown (0) if connection initiations
>               to all local IP addresses are accepted.";
> 
> NEW:
>               The value
>               should be unspecified (0) if connection initiations
>               to all local IP addresses are accepted.";
> 
> (there is another occurrence of "unknown (0)" that should be fixed as well)
> 
> Thank you.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : tcpm <[e-mail]> De la part de Scharf, Michael
> > Envoyé : vendredi 17 juin 2022 11:46
> > À : [e-mail]
> > Cc : [e-mail]
> > Objet : [tcpm] New version for draft-ietf-tcpm-yang-tcp
> >
> > Hi all,
> >
> > The authors have published a new version -07 of draft-ietf-tcpm-
> > yang-tcp. The long delay was mostly my fault, as my teaching day
> > job keeps me busy.
> >
> > draft-ietf-tcpm-yang-tcp got quite some comments during IETF last
> > call. In addition to directorate reviews, there were also further
> > comments (see the TCPM list archive). As a result, -07 includes a
> > number of changes. The diff can be seen at:
> >
> >  https://www.ietf.org/rfcdiff?url2=draft-ietf-tcpm-yang-tcp-07
> >
> > I'd like to highlight several changes that may be relevant to
> > TCPM:
> >
> > 1/ There was a request to better align with the TCP MIB. We have
> > not fully followed that request given TCPM decided against that in
> > the past. Nonetheless, we have added the TCP connection state to
> > the connection list similar to the TCP MIB. The state description
> > follows 793bis. One specific question is whether it actually makes
> > sense to have a state "closed". For -07, we have decided to model
> > the state "closed".
> >
> > 2/ The TCP MIB includes a TCP listener table. We have added a
> > corresponding list in -07. This again raises some subtle
> > questions, most notably, how to model a TCP listener that accepts
> > connections on any IPv4 and IPv6 address. The model in -07 allows
> > this
> >
> > 3/ The modeling of TCP-AO authentication parameters has changed.
> > The TCP-AO configuration has been moved to the key-chain, i.e.,
> > the TCP model now augments the YANG model in RFC 8177. This should
> > better align with running code. As far as we know, all router
> > operating systems configure TCP-AO via the key-chain. The model
> > now follows that approach, too.
> >
> > Please let us know if there are any comments regarding the new
> > version -07. It is possible that a follow-up -08 may be needed
> > soon-ish.
> >
> > Thanks
> >
> > Michael
> >
> >
> > -----Original Message-----
> > From: tcpm <[e-mail]> On Behalf Of internet-
> > [e-mail]
> > Sent: Thursday, June 16, 2022 6:03 PM
> > To: [e-mail]
> > Cc: [e-mail]
> > Subject: [tcpm] I-D Action: draft-ietf-tcpm-yang-tcp-07.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > This draft is a work item of the TCP Maintenance and Minor
> > Extensions WG of the IETF.
> >
> >         Title           : A YANG Model for Transmission Control
> > Protocol (TCP) Configuration and State
> >         Authors         : Michael Scharf
> >                           Mahesh Jethanandani
> >                           Vishal Murgai
> > 	Filename        : draft-ietf-tcpm-yang-tcp-07.txt
> > 	Pages           : 28
> > 	Date            : 2022-06-16
> >
> > Abstract:
> >    This document specifies a minimal YANG model for TCP on devices
> > that
> >    are configured and managed by network management protocols.
> > The YANG
> >    model defines a container for all TCP connections, and
> > groupings of
> >    authentication parameters that can be imported and used in TCP
> >    implementations or by other models that need to configure TCP
> >    parameters.  The model also includes basic TCP statistics.  The
> > model
> >    is compliant with Network Management Datastore Architecture
> > (NMDA)
> >    (RFC 8342).
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-tcpm-yang-tcp/
> >
> > There is also an htmlized version available at:
> > https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-yang-tcp-07
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-tcpm-yang-tcp-07
> >
> >
> > Internet-Drafts are also available by rsync at
> > rsync.ietf.org::internet-drafts
> >
> >
> > _______________________________________________
> > tcpm mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/tcpm
> >
> > _______________________________________________
> > tcpm mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/tcpm
> 
> __________________________________________________________
> __________________________________________________________
> _____
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
> message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.