Re: [netmod] WG Last Call: draft-ietf-netmod-yang-instance-file-format-06 to -07
Hi Balazs, > Have the YANG modules been validated and tested for formatting? > > (i.e., pyang -f yang --keep-comments --yang-line-length 69 filename) > > BALAZS: yes. With pyang offline and yangvalidator.com Okay. > Have the examples in the draft validated against the YANG module? > > BALAZS: Only manually. How do you validate samples conforming to a yang data > structure ? Hmmm, seeing that the examples are still not valid, here goes: Until such time as tools support validating structure-data-ext, one can rewrite the YANG module via s/sx:structure/container/ and perform the validation against the resulting YANG module. > Please review the Normative/Informative status of the references. > > Not looking carefully, but RFCs 2119 and 8174 should be Normative, > > and I think RFCs 3688 and 6020 should be Informative, right? > > BALAZS: OK, changed in rev 08 Did you check all the other references too? (I’m trying to save having to do another roundtrip when I do the shepherd writeup...) > All of the “import” statements in the YANG module are missing a > > “reference” statement. > > BALAZS: > > Added: > > rfc6991 for types added. > > Already present: > > rfc8342 for datastores > > ietf-netmod-yang-data-ext for ietf-yang-structure-ext Again, all the “import” statements in the YANG module are missing a “reference” statement. > Please add a paragraph to Section 5.2 preceding the YANG module > > indicating all the aforementioned Normative references. > > BALAZS: OK, I did it, but > > this is not what is required by > https://tools.ietf.org/html/rfc8407#section-3.9. > > I also see no value in this statement. I the "reference” statements mentioned above had been added, then s3.9 applies. > The copyright in the YANG module needs to be 2020 (not 2019) > > BALAZS: OK > > > > Please ensure a blank line between paragraphs in the “description" > > statements. > > BALAZS: OK > > > > Please add a statement to the Introduction regarding why the module > > Isn’t compliant with NMDA. > > BALAZS: Sorry, don’t understand. Why is this not compliant with NMDA ? > > IMHO it is NMDA compliant, or rather it has nothing to do with NDMA. Either way but, per https://tools.ietf.org/html/rfc8407#section-3.5, the statement should be in the Introduction section. > The tree diagram does not adhere to the syntax described in > > draft-ietf-netmod-yang-data-ext. > > BALAZS: OK I try, but what actually is the problem? Any help would be really > appreciated. I was looking at the “+—rw”, which can’t be right because yang-data is not “configuration”... > Sadly > > pyang -p ../ietfYams ietf-yang-instance-data\@2020-03-06.yang -f tree > --tree-print-yang-data --tree-print-yang-data > > doesn’t print out anything, so I am handcrafting. `pyang` supports the old/RFC8040 “rc:yang-data” statement; it hasn’t been updated to support the new "sx:structure” statement. > I just updated pyang from git. Any idea why this doesn’t work for me? > > It would be good if YangValidator would print out the tree. At some point it > did. Not now. :-( First, use the s/sx:structure/container/ trick mentioned above. Then s/+--rw/+—/. Then review https://tools.ietf.org/html/draft-ietf-netmod-yang-data-ext-05#section-3 and tweak accordingly until all is good. > Please update the first sentence in Section 5.1 to also reference > draft-ietf-netmod-yang-data-ext. > > BALZS: OK > > > > Please ensure that the planning-text version of the draft passes > > IDNITS (https://www6.ietf.org/tools/idnits) at the “verbose output” > > level and correct any issues found, or explain why they shouldn’t > > be corrected. > > BALAZS: OK, corrected Thanks! (this is almost always the cause for needing another draft update when doing the shepherd writeup) NEW: looking at the new "format-version”, please add a pattern statement to constrain the string values appropriately. Hint, it’s half a "date-and-time” type... Kent // contributor (and shepherd) ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
[netmod] Protocol Action: 'YANG Module Tags' to Proposed Standard (draft-ietf-netmod-module-tags-10.txt)
The IESG has approved the following document: - 'YANG Module Tags' (draft-ietf-netmod-module-tags-10.txt) as Proposed Standard This document is the product of the Network Modeling Working Group. The IESG contact persons are Warren Kumari, Ignas Bagdonas and Alissa Cooper. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-module-tags/ Technical Summary This document provides for the association of tags with YANG modules. The expectation is for such tags to be used to help classify and organize modules. A method for defining, reading and writing modules’ tags is provided. Tags may be standardized and assigned during module definition, assigned by implementations, or dynamically defined and set by users. This document provides guidance to future model writers and, as such, this document updates RFC 8407. Working Group Summary The WG had significant questions on how module tags might be used. Section 1.1 of the document dwells on how and why module tags are applied, addressing significant points in this discussion from the vantage point of WG participants. Possible usage of the module tags was the most controversial part of the document progress, which eventually came to consensus. Document Quality There is a substantial interest from the model user community to have module tags functionality available. The document has received significant reviews, including vigorous WG debate that resulted in significant changes to the document and multiple WG last calls. YANG doctors have reviewed the document. Personnel Joel Jaeggli is the Document Shepherd for this document. Alissa Cooper is the Responsible Area Director. IANA Note The document defines two new IANA registries (YANG Module Tag Prefixes Registry and YANG Module Tags Registry), and adds entries to two existing IANA registries (IETF XML Registry and YANG Modules Names Registry). ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
[netmod] Alexey Melnikov's No Objection on draft-ietf-netmod-module-tags-10: (with COMMENT)
Alexey Melnikov has entered the following ballot position for draft-ietf-netmod-module-tags-10: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-netmod-module-tags/ -- COMMENT: -- Thank you for addressing my DISCUSS and my apologies for taking so long. ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
Re: [netmod] Question in Schema Mount
Hi, SAMIER BARGUIL GIRALDO wrote: > Hi, > > It is posible to mount just part of other yang module (i.e. just the "state" > branch) using the current definition? Section 1 of RFC 8528 says: This document allows mounting of complete data models only. /martin > > > Samier Barguil > Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de > Transporte | > > Móvil +57 3017026430 > > Móvil +34 665416074 > > E-mail samier.barguilgiraldo@telefonica.com > > E-mail samier.barg...@wipro.com > > > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, > puede contener información privilegiada o confidencial y es para uso > exclusivo de la persona o entidad de destino. Si no es usted. el destinatario > indicado, queda notificado de que la lectura, utilización, divulgación y/o > copia sin autorización puede estar prohibida en virtud de la legislación > vigente. Si ha recibido este mensaje por error, le rogamos que nos lo > comunique inmediatamente por esta misma vía y proceda a su destrucción. > > The information contained in this transmission is privileged and confidential > information intended only for the use of the individual or entity named > above. If the reader of this message is not the intended recipient, you are > hereby notified that any dissemination, distribution or copying of this > communication is strictly prohibited. If you have received this transmission > in error, do not read it. Please immediately reply to the sender that you > have received this communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, > pode conter informação privilegiada ou confidencial e é para uso exclusivo da > pessoa ou entidade de destino. Se não é vossa senhoria o destinatário > indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia > sem autorização pode estar proibida em virtude da legislação vigente. Se > recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente > por esta mesma via e proceda a sua destruição ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
[netmod] I-D Action: draft-ietf-netmod-yang-instance-file-format-09.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network Modeling WG of the IETF. Title : YANG Instance Data File Format Authors : Balazs Lengyel Benoit Claise Filename: draft-ietf-netmod-yang-instance-file-format-09.txt Pages : 27 Date: 2020-03-17 Abstract: There is a need to document data defined in YANG models when a live server is not available. Data is often needed already at design or implementation time or needed by groups that do not have a live running server available. This document specifies a standard file format for YANG instance data, which follows the syntax and semantics of existing YANG models, and annotates it with metadata. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-instance-file-format/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-netmod-yang-instance-file-format-09 https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-instance-file-format-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-yang-instance-file-format-09 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/ ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
[netmod] I-D Action: draft-ietf-netmod-yang-schema-comparison-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network Modeling WG of the IETF. Title : YANG Schema Comparison Author : Robert Wilton Filename: draft-ietf-netmod-yang-schema-comparison-00.txt Pages : 13 Date: 2020-03-17 Abstract: This document specifies an algorithm for comparing two revisions of a YANG schema to determine the scope of changes, and a list of changes, between the revisions. The output of the algorithm can be used to help select an appropriate revision-label or YANG semantic version number for a new revision. This document defines a YANG extension that provides YANG annotations to help the tool accurately determine the scope of changes between two revisions. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-schema-comparison/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-netmod-yang-schema-comparison-00 https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-schema-comparison-00 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/ ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
Re: [netmod] Adoption of versioning design team docs
On Mar 17, 2020, at 08:15, Lou Berger mailto:lber...@labn..net>> wrote: All, The adoption call ended yesterday. While there is clearly work to do to reach consensus on these documents, they are all adopted as the starting point for the solutions that the WG will develop on these topics. Normal working group processing of these documents will continue on these documents. This includes revisiting intended status of each document before submission for publication to the IESG. We thank the design team for their hard work and important contributions! Authors, Please repos each document, with only the file name and publication date changed. The file names should all be in the form draft-ietf-netmod-. All documents have been reposted as WG documents with -00 rev. I have updated replaces, too. I think two of them need your approval as Rob was the only listed author on them. Joe ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
[netmod] I-D Action: draft-ietf-netmod-yang-semver-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network Modeling WG of the IETF. Title : YANG Semantic Versioning Authors : Benoit Claise Joe Clarke Reshad Rahman Robert Wilton Balazs Lengyel Jason Sterne Kevin D'Souza Filename: draft-ietf-netmod-yang-semver-00.txt Pages : 15 Date: 2020-03-17 Abstract: This document specifies a scheme for applying a modified set of semantic versioning rules to revisions of YANG modules. Additionally, this document defines a revision label for this modified semver scheme based on the specification in draft-verdt- netmod-yang-module-versioning. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-semver/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-netmod-yang-semver-00 https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-semver-00 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/ ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
[netmod] I-D Action: draft-ietf-netmod-yang-ver-selection-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network Modeling WG of the IETF. Title : YANG Schema Selection Authors : Robert Wilton Reshad Rahman Joe Clarke Jason Sterne Bo Wu Filename: draft-ietf-netmod-yang-ver-selection-00.txt Pages : 32 Date: 2020-03-17 Abstract: This document defines a mechanism to allow clients, using NETCONF or RESTCONF, to configure and select YANG schema for interactions with a server. This functionality can help servers support clients using older revisions of YANG modules even if later revisions contain non- backwards-compatible changes. It can also be used to allow clients to select between YANG schema defined by different organizations. This draft provides a solution to YANG versioning requirements 3.1 and 3.2. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-ver-selection/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-netmod-yang-ver-selection-00 https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-ver-selection-00 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/ ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
[netmod] I-D Action: draft-ietf-netmod-yang-packages-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network Modeling WG of the IETF. Title : YANG Packages Authors : Robert Wilton Reshad Rahman Joe Clarke Jason Sterne Bo Wu Filename: draft-ietf-netmod-yang-packages-00.txt Pages : 56 Date: 2020-03-17 Abstract: This document defines YANG packages, a versioned organizational structure holding a set of related YANG modules, that collectively define a YANG schema. It describes how packages: are represented on a server, can be defined in offline YANG instance data documents, and can be used to define the schema associated with YANG instance data documents. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-packages/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-00 https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-packages-00 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/ ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
[netmod] I-D Action: draft-ietf-netmod-yang-module-versioning-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network Modeling WG of the IETF. Title : Updated YANG Module Revision Handling Authors : Benoit Claise Joe Clarke Reshad Rahman Robert Wilton Balazs Lengyel Jason Sterne Kevin D'Souza Filename: draft-ietf-netmod-yang-module-versioning-00.txt Pages : 34 Date: 2020-03-17 Abstract: This document specifies a new YANG module update procedure that can document when non-backwards-compatible changes have occurred during the evolution of a YANG module. It extends the YANG import statement with an earliest revision filter to better represent inter-module dependencies. It provides help and guidelines for managing the lifecycle of YANG modules and individual schema nodes. This document updates RFC 7950, RFC 8407 and RFC 8525. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-module-versioning/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-netmod-yang-module-versioning-00 https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-module-versioning-00 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/ ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
Re: [netmod] Adoption of versioning design team docs
All, The adoption call ended yesterday. While there is clearly work to do to reach consensus on these documents, they are all adopted as the starting point for the solutions that the WG will develop on these topics. Normal working group processing of these documents will continue on these documents. This includes revisiting intended status of each document before submission for publication to the IESG. We thank the design team for their hard work and important contributions! Authors, Please repos each document, with only the file name and publication date changed. The file names should all be in the form draft-ietf-netmod-. Thank you, Lou (and Kent and Joel) On 3/2/2020 5:29 PM, Lou Berger wrote: Hi, We'd like to start a two week adoption call for the set of documents described below by Rob. To be specific, this includes 1) draft-verdt-netmod-yang-solutions-03 2) draft-verdt-netmod-yang-module-versioning-01 3) draft-verdt-netmod-yang-semver-01 4) draft-rwilton-netmod-yang-packages-03 5) draft-wilton-netmod-yang-ver-selection-02 6) draft-verdt-netmod-yang-schema-comparison-00 The adoption call ends in two weeks, on March 16. Please voice your support or objections on list. While we prefer to adopt as a set, objections on specific documents are acceptable. Netmod Chairs On 2/29/2020 2:21 AM, Rob Wilton (rwilton) wrote: Netmod chairs, The version selection draft draft-wilton-netmod-yang-ver-selection-02 is now posted. With that, the YANG versioning design team would like to please request you make an WG adoption call for these documents. The updated full list is: 1) draft-verdt-netmod-yang-solutions-03 - Solution overview, updated since 106 to cover updates to version selection and schema comparison drafts. 2) draft-verdt-netmod-yang-module-versioning-01 - Base module versioning solution, unchanged from the version presented at 106. 3) draft-verdt-netmod-yang-semver-01 - YANG Semantic version numbers, unchanged from the version presented at 106. 4) draft-rwilton-netmod-yang-packages-03 - YANG packages draft, updated since 106 5) draft-wilton-netmod-yang-ver-selection-02 - Version selection, updated since 106, as per notes below 6) draft-verdt-netmod-yang-schema-comparison-00 - Schema comparison tooling, unchanged from the version presented at 106. The main changes to the version selection draft are: - We have tried to simplify the model, but at the same time give servers more flexibility about how they implement version selection and what it can be used for. E.g. if the server wants to allow a client to choose between different schema versions, but require that all clients use the same schema version, that is now possible - The draft explicitly disallows schema-selection happening mid-session - The solution allows the server to require clients to configure schema-sets before they are used - The solution provides more information about which schema-sets are compatible with each other Regards, Rob ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
Re: [netmod] Adoption of versioning design team docs
[As a contributor] I mostly agree with Martin’s comments, mostly in that I don’t think the “semver" label has been fully justified relative to the disruption I perceive it may cause. I’d prefer the documents regarding semver be adopted as Experimental until more is known. Kent > On Mar 13, 2020, at 12:53 PM, Sterne, Jason (Nokia - CA/Ottawa) > wrote: > > Hi Martin, > > Thanks for taking a look at the drafts and for your support of the DT's work. > Please see inline. > > Regards, > Jason > >> -Original Message- >> From: netmod On Behalf Of Martin Björklund >> Sent: Tuesday, March 10, 2020 3:28 PM >> To: lber...@labn.net >> Cc: netmod-cha...@ietf.org; netmod@ietf.org >> Subject: Re: [netmod] Adoption of versioning design team docs >> >> [second attempt, sorry for duplicates] >> >> Hi, >> >> By document: >> >> draft-verdt-netmod-yang-module-versioning-01 >> >> This is a great contribution to the YANG ecosystem. It is very well >> written, and I would like to see this document proceed quickly. The >> solutions it proposed are really needed. I have one objection >> though; in 7.1 the text says: >> >>All IETF YANG modules MUST include revision-label statements for all >>newly published YANG modules, and all newly published revisions of >>existing YANG modules. The revision-label MUST take the form of a >>YANG semantic version number [I-D.verdt-netmod-yang-semver]. >> >> I strongly disagree with this new rule. IETF modules use a linear >> history, so there are no reasons to use "modified semver". > > [>>JTS: ] This point will obviously require further discussion, so we have > raised an issue in our GitHub DT tracker for it: > https://github.com/netmod-wg/yang-ver-dt/issues/45 > > Would you be okay to defer discussion on this until after the adoption call, > so that we can focus discussion on the two drafts that you oppose adopting? > >> >> I support the adoption of this document. >> >> (I will send a review of this document in a separate mail) >> >> >> draft-verdt-netmod-yang-semver-01 >> >> This draft proposes a way to express how a given revision is >> backwards compatible in a very short format. With the new extension >> statements in draft-verdt-netmod-yang-module-versioning, this >> information is already present in the revision history of a module. >> (One possible exception is editorial changes, but that can easily be >> fixed by adding an "editorial" extension to "ietf-yang-revisions"). >> >> I don't think this document should be adopted. > > [>>JTS: ] History suggests that YANG modules, even those produced by IETF > will not always be flawless. Most IETF documents may end up having a linear > history (in which case semver and the modified semver look the same). But > some may not. > > Vendors, however, definitely need to be able to support/fix issues in shipped > releases without forcing clients to move to the latest code. That means some > ability to describe changes in branched modules is required. Branching is > optional (and NBC changes in previous versions is not recommended) but when > it does need to happen, we should at least have a standardized and well > described mechanism available. > > Semver provides a lot more intuitive high level information about the scope > of changes in a module vs a vanilla revision date. It presents a human > friendly approximation/summary for a complex lineage system when needed. > > Having a common modified yang semver scheme for standard and vendor models > would be very useful for consumers of YANG models. > > Ultimately a diff of modules is needed to know every change, but it does give > a quick 1 line indication of the impact of changing between two module > versions, and can handle branched model development. > >> >> >> draft-rwilton-netmod-yang-packages-03 >> >> I support the adoption of this document. >> >> >> draft-wilton-netmod-yang-ver-selection-02 >> >> I think the solutions proposed in this draft are overly complex and >> some of them are probably impossible to implement correctly in real >> world use cases. >> >> I don't think this document should be adopted. > > > [>>JTS: ] It would be good to discuss the scenarios that version selection > may not work for. > > We do believe there are some cases where version selection is very helpful. > > One example is when an NBC change needs to occur (e.g. bug fix, or extending > functionality) that causes a leaf to change type but there is a strong desire > to keep the same name (e.g. something basic like "interface" or "address"). > We can't use a "status deprecated" approach to support the old functionality > in this case. > > Another example is the ability for a client to specify (and a server to > advertise & limit) which data models (3rd party vs proprietary) it wants to > use for interactions with the server. > > This is an important part of a complete solution to versioning
Re: [netmod] Question in Schema Mount
Hi, It is posible to mount just part of other yang module (i.e. just the "state" branch) using the current definition? Regards Samier Barguil Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte | Móvil +57 3017026430 Móvil +34 665416074 E-mail samier.barguilgiraldo@telefonica.com E-mail samier.barg...@wipro.com Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição ___ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
