Hi,
This I-D is currently doing the following -
- Providing clarifications/description to text in RFC 8231 ->
[Clarification]
- Further, adding examples to describe that processing -> [Example]
- Updating RFC 8231 by changing some behavior -> [Update]
The first two is Informational content. IMHO the Informational content
should not use normative keywords (if there is a need to add MUST, SHOULD,
etc, then perhaps it should be in the update portion).
This is my understanding of the current text ->
3. PCEP LSP Database [Clarification]
3.1. Structure [Clarification]
3.2. Synchronization [Clarification]
3.3. Stateful Bringup [Update]
3.3.1. Updates to RFC 8231 [Update][Example]
3.4. Successful MBB [Example]
3.5. Aborted MBB [Example]
4. PCEP Association Database [Clarification]
4.1. 2 LSPs in same Association [Example]
4.2. Switch Association during MBB [Example]
5. Computation Constraints [Update(?)]
6. Use of SR-RRO and SRv6-RRO objects [Update]
Now, how to progress this I-D? I see the following options -
- Break it into two documents, one informational with clarification and
examples, one standards track
- Same document but a clear separation of informational and normative
content
- Status quo
It would be good to get feedback from WG on this! Looking forward to the
dicussion!
Thanks!
Dhruv
_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce
