From 97583eb8ed5f7136137ebd57202fabf1cf207681 Mon Sep 17 00:00:00 2001 From: ID Bot Date: Mon, 27 Nov 2023 12:09:55 +0000 Subject: [PATCH] Script updating gh-pages from 236355a. [ci skip] --- draft-ietf-lamps-rfc4210bis.html | 8 +++++++- draft-ietf-lamps-rfc4210bis.txt | 7 +++++++ 2 files changed, 14 insertions(+), 1 deletion(-) diff --git a/draft-ietf-lamps-rfc4210bis.html b/draft-ietf-lamps-rfc4210bis.html index f24cb27..6f41aac 100644 --- a/draft-ietf-lamps-rfc4210bis.html +++ b/draft-ietf-lamps-rfc4210bis.html @@ -3577,6 +3577,9 @@
NestedMessageContent ::= PKIMessages +

In case an RA needs to modify a request message, it MAY include the original +PKIMessage in the generalInfo field of the modified message as described in +Section 5.1.1.3.

@@ -7820,7 +7823,10 @@

Some editorial changes to Section 5.1.3.4 and Appendix E after discussion with David resolving #30 and discussing at IETF 117

  • -

    Fixed some references in Section 5.2.8.3 which broke from RFC2510 to RFC4210

    +

    Added a cross-reference to Section 5.1.1.3 regarding use of OrigPKIMessage to Section 5.1.3.5

    +
    • +
  • +

    Fixed some references in Section 5.2.8.3 which broke from RFC2510 to RFC4210

    • From version 06 -> 07:

    diff --git a/draft-ietf-lamps-rfc4210bis.txt b/draft-ietf-lamps-rfc4210bis.txt index 6551a9e..f671412 100644 --- a/draft-ietf-lamps-rfc4210bis.txt +++ b/draft-ietf-lamps-rfc4210bis.txt @@ -1959,6 +1959,10 @@ Table of Contents NestedMessageContent ::= PKIMessages + In case an RA needs to modify a request message, it MAY include the + original PKIMessage in the generalInfo field of the modified message + as described in Section 5.1.1.3. + 5.2. Common Data Structures Before specifying the specific types that may be placed in a PKIBody, @@ -5759,6 +5763,9 @@ Appendix G. History of Changes * Some editorial changes to Section 5.1.3.4 and Appendix E after discussion with David resolving #30 and discussing at IETF 117 + * Added a cross-reference to Section 5.1.1.3 regarding use of + OrigPKIMessage to Section 5.1.3.5 + * Fixed some references in Section 5.2.8.3 which broke from RFC2510 to RFC4210