Re-, Please see inline.
Cheers, Med De : Benoit Claise [mailto:[email protected]] Envoyé : vendredi 11 août 2017 14:50 À : BOUCADAIR Mohamed IMT/OLN; [email protected]; [email protected]; [email protected] Objet : Re: YANG validation issue with draft-ietf-softwire-dslite-yang-05.txt Hi Med, That's very good that you are NMDA compliant. I didn't pay much attention and thought that both ietf-dslite-aftr@2017-08-10 and [email protected]<mailto:[email protected]> were part of draft-ietf-softwire-dslite-yang-05.txt [Med] We used to have both NAT and softwire aspects covered in the same module, but that design is not clean. We need to separate both. Actually [email protected]<mailto:[email protected]> comes from https://datatracker.ietf.org/doc/draft-sivakumar-yang-nat/ Since ietf-dslite-aftr@2017-08-10 imports [email protected]<mailto:[email protected]>, the next step is to modify [email protected]<mailto:[email protected]> to be NMDA compliant, right? [Med] Yes, we will publish the new NAT module soon. Also, how can draft-ietf-softwire-dslite-yang progress without progressing this normative reference? [Med] There is a call for adoption of the NAT YANG in OPSAWG : https://www.ietf.org/mail-archive/web/opsawg/current/msg04975.html. 8.1. Normative references [I-D.sivakumar-yang-nat] Sivakumar, S., Boucadair, M., and S. Vinapamula, "YANG Data Model for Network Address Translation (NAT)", draft- sivakumar-yang-nat-07 (work in progress), July 2017. Regards, Benoit Hi Benoit, Please see inline. Cheers, Med -----Message d'origine----- De : Benoit Claise [mailto:[email protected]] Envoyé : vendredi 11 août 2017 11:01 À : [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Objet : YANG validation issue with draft-ietf-softwire-dslite-yang-05.txt Dear authors, I see that you posted a new version, but there are still some errors See http://www.claise.be/IETFYANGPageCompilation.html See https://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-yang/ => YANG validation OLD: augment "/nat:nat-module/nat:nat-instances/nat:nat-instance" { NEW: I guess this should be augment "/nat:nat-config/nat:nat-instances/nat:nat-instance" { [Med] Actually, the OLD one is correct. We changed the NAT module to be aligned with the NDMA recommendation (so, we don't have any more nat-config) OLD: augment "/nat:nat-module/nat:nat-instances/nat:nat-instance/nat:mapping- table/nat:mapping-entry"{ NEW: I guess this should be augment "/nat:nat-state/nat:nat-instances/nat:nat-instance/nat:mapping- table/nat:mapping-entry"{ [Med] Idem as above. We don't have anymore a nat-state in the new NAT module. Attached is the updated YANG module that validates. [Med] Thank you. Regards, Benoit
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
