Re: [lamps] New Version Notification for draft-richardson-lamps-rfc7030-csrattrs-04.txt

[Michael Richardson <[e-mail]>]

Hi,

[e-mail] wrote:
    > Diff:           https://www.ietf.org/rfcdiff?url2=draft-richardson-lamps-rfc7030-csrattrs-04


  0  90: SEQUENCE {
  2  88:   SEQUENCE {
  4   9:     OBJECT IDENTIFIER extensionRequest (1 2 840 113549 1 9 14)
 15  75:     SET {
 17  73:       SEQUENCE {
 19   3:         OBJECT IDENTIFIER subjectAltName (2 5 29 17)
 24   3:         [0] {
 26   1:           BOOLEAN TRUE
       :           }
 29  61:         SEQUENCE {
 31  59:           [0] {
 33  57:             UTF8String
       :               '[e-mail]'
       :               'ample.com'
       :             }
       :           }
       :         }
       :       }
       :     }
       :   }

so it contains the entire ExtensionRequest now as suggested by Sean Turner.
(I had to write code to generate this correctly, but I'm not quite finished
processing it)

The other known examples need to be filled in, and we need to make sure our list of
examples covers all the existing use cases that are out there.   So there are
both known unknowns and there may be unknown unknowns to add, but the known
knowns are now filled in.

At this point, I think it would be appropriate to review for WG Adoption.

I think that the document should Updates (Amends) RFC7030 and RFC8995 and RFC9148.

It is normatively referenced by:
   anima-brski-cloud
   acme-intergrations
   anima-brski-prm
   anima-brski-ae


--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-