RE: Comments on draft-ietf-hubmib-efm-mib-02.txt
"Romascanu, Dan \(Dan\)" <[email protected]>
| Newsgroups | gmane.ietf.hubmib |
|---|---|
| Message-ID | <AAB4B3D3CF0F454F98272CBE187FDE2F07FA6BCA@IS0004AVEXU1.global.avaya.com> |
I did not receive yet any directives on this respect. Please continue to use 3667, unless you hear from me.
Regards,
Dan
Checking nits according to http://www.ietf.org/ID-Checklist.html :
Checking conformance with RFC 3667/3668 boilerplate...
* The document claims conformance with section 10 of RFC 2026, but uses
some RFC 3667/3668 boilerplate. As RFC 3667/3668 replaces section 10 of RFC
2026, you should not claim conformance with it if you have changed to using
RFC 3667/3668 boilerplate.
Changed to 3667 boilerplate (which is probably already outdated!). Are we supposed to jump to the newest 3997/3998 stuff yet?
.
_______________________________________________
Hubmib mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/hubmib