Skip to main content

Local Protection Enforcement in PCEP
draft-ietf-pce-local-protection-enforcement-08

Revision differences

Document history

Date Rev. By Action
2022-11-17
08 Andrew Stone New version available: draft-ietf-pce-local-protection-enforcement-08.txt
2022-11-17
08 (System) New version approved
2022-11-17
08 (System) Request for posting confirmation emailed to previous authors: Andrew Stone , Mustapha Aissaoui , Samuel Sidor , Siva Sivabalan
2022-11-17
08 Andrew Stone Uploaded new revision
2022-11-16
07 Donald Eastlake Request for Early review by RTGDIR Completed: Has Nits. Reviewer: Donald Eastlake.
2022-10-17
07 Luc André Burdet Request for Early review by RTGDIR is assigned to Donald Eastlake
2022-10-17
07 Luc André Burdet Request for Early review by RTGDIR is assigned to Donald Eastlake
2022-10-17
07 Luc André Burdet Assignment of request for Early review by RTGDIR to John Drake was marked no-response
2022-08-17
07 Haomian Zheng Request for Early review by RTGDIR is assigned to John Drake
2022-08-17
07 Haomian Zheng Request for Early review by RTGDIR is assigned to John Drake
2022-08-17
07 John Scudder Requested Early review by RTGDIR
2022-08-10
07 Julien Meuric
## Document History

1.  Does the working group (WG) consensus represent the strong concurrence of a
    few individuals, with others being silent, or …
## Document History

1.  Does the working group (WG) consensus represent the strong concurrence of a
    few individuals, with others being silent, or did it reach broad agreement?
-> Concurrence of a few individuals, with others being silent
  (update following interop tests)

2.  Was there controversy about particular points, or were there decisions where
    the consensus was particularly rough?
-> No

3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
  so, please summarize the areas of conflict in separate email messages to the
  responsible Area Director. (It should be in a separate email because this
  questionnaire is publicly available.)
-> No

4. For protocol documents, are there existing implementations of the contents of
  the document?
-> Yes
Have a significant number of potential implementers indicated
  plans to implement?
-> Yes
Are any existing implementations reported somewhere,
  either in the document itself (as [RFC 7942][3] recommends) or elsewhere
  (where)?
-> Cf. Section 6 of the document.

## Additional Reviews

5. Do the contents of this document closely interact with technologies in other
  IETF working groups or external organizations, and would it therefore benefit
  from their review? Have those reviews occurred? If yes, describe which
  reviews took place.
-> Links with RSVP-TE (TEAS & MPLS WGs) and Segment Routing (Spring WG).
  Reviews would be welcome.

6. Describe how the document meets any required formal expert review criteria,
  such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.
-> N/A

7. If the document contains a YANG module, has the final version of the module
  been checked with any of the [recommended validation tools][4] for syntax and
  formatting validation? If there are any resulting errors or warnings, what is
  the justification for not fixing them at this time? Does the YANG module
  comply with the Network Management Datastore Architecture (NMDA) as specified
  in [RFC 8342][5]?
-> N/A

8. Describe reviews and automated checks performed to validate sections of the
  final version of the document written in a formal language, such as XML code,
  BNF rules, MIB definitions, CBOR's CDDL, etc.
-> N/A

## Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
  document is
- needed -> yes,
- clearly written -> yes,
- complete -> yes,
- correctly designed -> yes,
- ready to be handed off to the responsible Area Director? -> yes

10. Several IETF Areas have assembled [lists of common issues that their
    reviewers encounter][6]. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?
-> N/A

11. What type of RFC publication is being requested on the IETF stream ([Best
    Current Practice][12], [Proposed Standard, Internet Standard][13],
    [Informational, Experimental or Historic][14])?
-> Proposed Standard
Why is this the proper type of RFC?
-> It updates a PS protocol.
Do all Datatracker state attributes correctly reflect this intent?
-> Yes

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in [BCP 79][8]?
-> Yes
To the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.
-> The authors were requested to respond about the IPR policy.
  [https://mailarchive.ietf.org/arch/msg/pce/LbOePvX814Apdrho3Al81Peb3yc/]

13. Has each author, editor, and contributor shown their willingness to be
    listed as such?
-> Yes
If the total number of authors and editors on the front page
    is greater than five, please provide a justification.
-> 4 authors

14. Document any remaining I-D nits in this document. Simply running the [idnits
    tool][8] is not enough; please review the ["Content Guidelines" on
    authors.ietf.org][15]. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)
-> Nits corrected after review.

15. Should any informative references be normative or vice-versa? See the [IESG
    Statement on Normative and Informative References][16].
-> No

16. List any normative references that are not freely available to anyone. Did
    the community have sufficient access to review any such normative
    references?
-> N/A

17. Are there any normative downward references (see [RFC 3967][9] and [BCP
    97
][10]) that are not already listed in the [DOWNREF registry][17]? If so,
    list them.
-> No

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear state?
    If so, what is the plan for their completion?
-> No

19. Will publication of this document change the status of any existing RFCs?
-> The document updates an RFC.
If so, does the Datatracker metadata correctly reflect this and are those RFCs
    listed on the title page, in the abstract, and discussed in the
    introduction?
-> Yes
If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see [RFC 8126][11]).
-> The IANA section is consistent.
  Only a flag is required, and it was already assigned through the early allocation process.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.
-> N/A

[1]: https://www.ietf.org/about/groups/iesg/
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
[4]: https://trac.ietf.org/trac/ops/wiki/yang-review-tools
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
[6]: https://trac.ietf.org/trac/iesg/wiki/ExpertTopics
[7]: https://www.rfc-editor.org/info/bcp79
[8]: https://www.ietf.org/tools/idnits/
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
[10]: https://www.rfc-editor.org/info/bcp97
[11]: https://www.rfc-editor.org/rfc/rfc8126.html
[12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5
[13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1
[14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2
[15]: https://authors.ietf.org/en/content-guidelines-overview
[16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
[17]: https://datatracker.ietf.org/doc/downref/
2022-08-09
07 Julien Meuric
## Document History

    Does the working group (WG) consensus represent the strong concurrence of a
    few individuals, with others being silent, …
## Document History

    Does the working group (WG) consensus represent the strong concurrence of a
    few individuals, with others being silent, or did it reach broad agreement?
-> Concurrence of a few individuals, with others being silent
  (update following interop tests)

    Was there controversy about particular points, or were there decisions where
    the consensus was particularly rough?
-> No

## Additional Reviews

5. Do the contents of this document closely interact with technologies in other
  IETF working groups or external organizations, and would it therefore benefit
  from their review? Have those reviews occurred? If yes, describe which
  reviews took place.
-> Links with RSVP-TE (TEAS & MPLS WGs) and Segment Routing (Spring WG).
  Reviews would be welcome.

6. Describe how the document meets any required formal expert review criteria,
  such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.
-> N/A

7. If the document contains a YANG module, has the final version of the module
  been checked with any of the [recommended validation tools][4] for syntax and
  formatting validation? If there are any resulting errors or warnings, what is
  the justification for not fixing them at this time? Does the YANG module
  comply with the Network Management Datastore Architecture (NMDA) as specified
  in [RFC 8342][5]?
-> N/A

8. Describe reviews and automated checks performed to validate sections of the
  final version of the document written in a formal language, such as XML code,
  BNF rules, MIB definitions, CBOR's CDDL, etc.
-> N/A

## Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
  document is
- needed -> yes,
- clearly written -> yes,
- complete -> yes,
- correctly designed -> yes,
- ready to be handed off to the responsible Area Director? -> yes

10. Several IETF Areas have assembled [lists of common issues that their
    reviewers encounter][6]. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?
-> N/A

11. What type of RFC publication is being requested on the IETF stream ([Best
    Current Practice][12], [Proposed Standard, Internet Standard][13],
    [Informational, Experimental or Historic][14])?
-> Proposed Standard
Why is this the proper type of RFC?
-> It updates a PS protocol.
Do all Datatracker state attributes correctly reflect this intent?
-> Yes

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in [BCP 79][8]?
-> Yes
To the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.
-> The authors were requested to respond about the IPR policy.
  [https://mailarchive.ietf.org/arch/msg/pce/LbOePvX814Apdrho3Al81Peb3yc/]

13. Has each author, editor, and contributor shown their willingness to be
    listed as such?
-> Yes
If the total number of authors and editors on the front page
    is greater than five, please provide a justification.
-> 4 authors

14. Document any remaining I-D nits in this document. Simply running the [idnits
    tool][8] is not enough; please review the ["Content Guidelines" on
    authors.ietf.org][15]. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)
-> Nits corrected after review.

15. Should any informative references be normative or vice-versa? See the [IESG
    Statement on Normative and Informative References][16].
-> No

16. List any normative references that are not freely available to anyone. Did
    the community have sufficient access to review any such normative
    references?
-> N/A

17. Are there any normative downward references (see [RFC 3967][9] and [BCP
    97
][10]) that are not already listed in the [DOWNREF registry][17]? If so,
    list them.
-> No

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear state?
    If so, what is the plan for their completion?
-> No

19. Will publication of this document change the status of any existing RFCs?
-> The document updates an RFC.
If so, does the Datatracker metadata correctly reflect this and are those RFCs
    listed on the title page, in the abstract, and discussed in the
    introduction?
-> Yes
If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see [RFC 8126][11]).
-> The IANA section is consistent.
  Only a flag is required, and it was already assigned through the early allocation process.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.
-> N/A

[1]: https://www.ietf.org/about/groups/iesg/
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
[4]: https://trac.ietf.org/trac/ops/wiki/yang-review-tools
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
[6]: https://trac.ietf.org/trac/iesg/wiki/ExpertTopics
[7]: https://www.rfc-editor.org/info/bcp79
[8]: https://www.ietf.org/tools/idnits/
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
[10]: https://www.rfc-editor.org/info/bcp97
[11]: https://www.rfc-editor.org/rfc/rfc8126.html
[12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5
[13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1
[14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2
[15]: https://authors.ietf.org/en/content-guidelines-overview
[16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
[17]: https://datatracker.ietf.org/doc/downref/

2022-08-09
07 Julien Meuric Responsible AD changed to John Scudder
2022-08-09
07 Julien Meuric IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up
2022-08-09
07 Julien Meuric IESG state changed to Publication Requested from I-D Exists
2022-08-09
07 Julien Meuric IESG process started in state Publication Requested
2022-08-09
07 Julien Meuric
## Document History

    Does the working group (WG) consensus represent the strong concurrence of a
    few individuals, with others being silent, …
## Document History

    Does the working group (WG) consensus represent the strong concurrence of a
    few individuals, with others being silent, or did it reach broad agreement?
-> Concurrence of a few individuals, with others being silent
  (update following interop tests)

    Was there controversy about particular points, or were there decisions where
    the consensus was particularly rough?
-> No

## Additional Reviews

5. Do the contents of this document closely interact with technologies in other
  IETF working groups or external organizations, and would it therefore benefit
  from their review? Have those reviews occurred? If yes, describe which
  reviews took place.
-> Links with RSVP-TE (TEAS & MPLS WGs) and Segment Routing (Spring WG).
  Reviews would be welcome.

6. Describe how the document meets any required formal expert review criteria,
  such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.
-> N/A

7. If the document contains a YANG module, has the final version of the module
  been checked with any of the [recommended validation tools][4] for syntax and
  formatting validation? If there are any resulting errors or warnings, what is
  the justification for not fixing them at this time? Does the YANG module
  comply with the Network Management Datastore Architecture (NMDA) as specified
  in [RFC 8342][5]?
-> N/A

8. Describe reviews and automated checks performed to validate sections of the
  final version of the document written in a formal language, such as XML code,
  BNF rules, MIB definitions, CBOR's CDDL, etc.
-> N/A

## Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
  document is
- needed -> yes,
- clearly written -> yes,
- complete -> yes,
- correctly designed -> yes,
- ready to be handed off to the responsible Area Director? -> yes

10. Several IETF Areas have assembled [lists of common issues that their
    reviewers encounter][6]. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?
-> N/A

11. What type of RFC publication is being requested on the IETF stream ([Best
    Current Practice][12], [Proposed Standard, Internet Standard][13],
    [Informational, Experimental or Historic][14])?
-> Proposed Standard
Why is this the proper type of RFC?
-> It updates a PS protocol.
Do all Datatracker state attributes correctly reflect this intent?
-> Yes

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in [BCP 79][8]?
-> Yes
To the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.
-> The authors were requested to respond about the IPR policy.
  [https://mailarchive.ietf.org/arch/msg/pce/LbOePvX814Apdrho3Al81Peb3yc/]

13. Has each author, editor, and contributor shown their willingness to be
    listed as such?
-> Yes
If the total number of authors and editors on the front page
    is greater than five, please provide a justification.
-> 4 authors

14. Document any remaining I-D nits in this document. Simply running the [idnits
    tool][8] is not enough; please review the ["Content Guidelines" on
    authors.ietf.org][15]. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)
-> Nits corrected after review.

15. Should any informative references be normative or vice-versa? See the [IESG
    Statement on Normative and Informative References][16].
-> No

16. List any normative references that are not freely available to anyone. Did
    the community have sufficient access to review any such normative
    references?
-> N/A

17. Are there any normative downward references (see [RFC 3967][9] and [BCP
    97
][10]) that are not already listed in the [DOWNREF registry][17]? If so,
    list them.
-> No

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear state?
    If so, what is the plan for their completion?
-> No

19. Will publication of this document change the status of any existing RFCs?
-> The document updates an RFC.
If so, does the Datatracker metadata correctly reflect this and are those RFCs
    listed on the title page, in the abstract, and discussed in the
    introduction?
-> Yes
If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see [RFC 8126][11]).
-> The IANA section is consistent.
  Only a flag is required, and it was already assigned through the early allocation process.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.
-> N/A

[1]: https://www.ietf.org/about/groups/iesg/
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
[4]: https://trac.ietf.org/trac/ops/wiki/yang-review-tools
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
[6]: https://trac.ietf.org/trac/iesg/wiki/ExpertTopics
[7]: https://www.rfc-editor.org/info/bcp79
[8]: https://www.ietf.org/tools/idnits/
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
[10]: https://www.rfc-editor.org/info/bcp97
[11]: https://www.rfc-editor.org/rfc/rfc8126.html
[12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5
[13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1
[14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2
[15]: https://authors.ietf.org/en/content-guidelines-overview
[16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
[17]: https://datatracker.ietf.org/doc/downref/

2022-08-08
07 Andrew Stone New version available: draft-ietf-pce-local-protection-enforcement-07.txt
2022-08-08
07 (System) New version approved
2022-08-08
07 (System) Request for posting confirmation emailed to previous authors: Andrew Stone , Mustapha Aissaoui , Samuel Sidor , Siva Sivabalan
2022-08-08
07 Andrew Stone Uploaded new revision
2022-06-23
06 Julien Meuric IETF WG state changed to WG Consensus: Waiting for Write-Up from In WG Last Call
2022-06-23
06 Julien Meuric Notification list changed to julien.meuric@orange.com because the document shepherd was set
2022-06-23
06 Julien Meuric Document shepherd changed to Julien Meuric
2022-06-23
06 Julien Meuric Changed consensus to Yes from Unknown
2022-06-23
06 Julien Meuric Intended Status changed to Proposed Standard from None
2022-06-20
06 Andrew Stone New version available: draft-ietf-pce-local-protection-enforcement-06.txt
2022-06-20
06 (System) New version approved
2022-06-20
06 (System) Request for posting confirmation emailed to previous authors: Andrew Stone , Mustapha Aissaoui , Samuel Sidor , Siva Sivabalan
2022-06-20
06 Andrew Stone Uploaded new revision
2022-06-07
05 Julien Meuric IETF WG state changed to In WG Last Call from WG Document
2022-05-04
05 Andrew Stone New version available: draft-ietf-pce-local-protection-enforcement-05.txt
2022-05-04
05 (System) New version approved
2022-05-04
05 (System) Request for posting confirmation emailed to previous authors: Andrew Stone , Mustapha Aissaoui , Samuel Sidor , Siva Sivabalan
2022-05-04
05 Andrew Stone Uploaded new revision
2022-03-20
04 Dhruv Dhody Added to session: IETF-113: pce  Mon-1300
2022-03-20
04 Dhruv Dhody Removed from session: IETF-113: pce  Tue-1300
2022-03-20
04 Dhruv Dhody Added to session: IETF-113: pce  Tue-1300
2022-01-30
04 Andrew Stone New version available: draft-ietf-pce-local-protection-enforcement-04.txt
2022-01-30
04 (System) New version approved
2022-01-30
04 (System) Request for posting confirmation emailed to previous authors: Andrew Stone , Mustapha Aissaoui , Samuel Sidor , Siva Sivabalan
2022-01-30
04 Andrew Stone Uploaded new revision
2021-08-05
03 Andrew Stone New version available: draft-ietf-pce-local-protection-enforcement-03.txt
2021-08-05
03 (System) New version accepted (logged-in submitter: Andrew Stone)
2021-08-05
03 Andrew Stone Uploaded new revision
2021-02-03
02 Andrew Stone New version available: draft-ietf-pce-local-protection-enforcement-02.txt
2021-02-03
02 (System) New version approved
2021-02-03
02 (System) Request for posting confirmation emailed to previous authors: Andrew Stone , Mustapha Aissaoui , Samuel Sidor , Siva Sivabalan
2021-02-03
02 Andrew Stone Uploaded new revision
2021-01-13
01 Samuel Sidor New version available: draft-ietf-pce-local-protection-enforcement-01.txt
2021-01-13
01 (System) New version accepted (logged-in submitter: Samuel Sidor)
2021-01-13
01 Samuel Sidor Uploaded new revision
2020-11-16
00 Andrew Stone This document now replaces draft-stone-pce-local-protection-enforcement instead of None
2020-11-16
00 Andrew Stone New version available: draft-ietf-pce-local-protection-enforcement-00.txt
2020-11-16
00 (System) New version accepted (logged-in submitter: Andrew Stone)
2020-11-16
00 Andrew Stone Uploaded new revision