Hi Mirja,
Thank you very much for your time and valuable comments.
Your comments are addressed inline below with prefix [HC].
Best Regards,
Huaimo
-----Original Message-----
From: Mirja Kuehlewind [mailto:[email protected]]
Sent: Wednesday, January 04, 2017 12:35 PM
To: The IESG
Cc: [email protected]; [email protected]; [email protected];
[email protected]; [email protected]
Subject: Mirja Kühlewind's No Objection on draft-ietf-ospf-ttz-05: (with
COMMENT)
Mirja Kühlewind has entered the following ballot position for
draft-ietf-ospf-ttz-05: 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-ospf-ttz/
----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------
Questions on IANA section (not an OSPF expert, so please excuse me if I
misunderstood something):
- Don't you have to register both LS types 9 and 10 somehow?
[HC]: LS types 9 and 10 are the existing types. No need to register them.
- And do the "Types for new TLVs in the new TTZ LSA" create a new
registry or is this an existing one?
[HC]: A new register needs to be created for "Types for new TLVs in the new TTZ
LSA". In section “IANA Considerations”, the following changes have been
proposed to and approved by IANA.
IANA is to create and maintain a new registry:
o OSPFv2 TTZ LSA TLVs
Initial values for the registry are given below.
Value OSPFv2 TTZ LSA TLV Name Definition
----- ----------------------- ----------
0 Reserved
1 TTZ ID TLV see section 6.2
2 TTZ Router TLV see section 6.3
3 TTZ Options TLV see section 6.4
4-32767 Unassigned
32768-65535 Reserved
The future assignments are to be made through IETF Review.
Other minor comments:
- What's a DR? Please spell this out!
[HC]: DR is short for Designated Router. We will spell it out in the document.
- There is only little normative language used in this doc. Potentially
some more normative language could make things clearer. However I don't
have concrete proposals what to change and I believe the most important
parts are in normative language. So there is no urgent need to change
anything but maybe another check would be good to make sure normative
language is used where needed.
[HC]: We will have another check for this and make sure normative language is
used wherever needed.
_______________________________________________
OSPF mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ospf
