Re: [Anima] Content-Transfer-Encoding and HTTP 1.x in ANIMA BRSKI

[Michael Richardson <[e-mail]>]

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Autonomic Networking Integrated Model and
> Approach WG of the IETF.

>        Title           : Bootstrapping Remote Secure Key Infrastructures (BRSKI)
>	 Filename        : draft-ietf-anima-bootstrapping-keyinfra-22.txt

> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-bootstrapping-keyinfra-22

I have added a section 6:

       6.  Clarification of transfer-encoding

 	   [RFC7030] defines it's endpoints to include a "Content-Transfer-
 	   Encoding" heading, and the payloads to be [RFC4648] Base64 encoded
 	   DER.

 	   When used within BRSKI, the original RFC7030 EST endpoints remain
 	   Base64 encoded, but the new BRSKI end points which send and receive
 	   binary artifacts (specifically, ../voucherrequest) are binary.  That
 	   is, no encoding is used.

 	   In the BRSKI context, the EST "Content-Transfer-Encoding" header if
 	   present, SHOULD be ignored.  This header does not need to included.

I have not made an informative reference to ietf-lamps-rfc7030est-clarify yet.

I will stop now for awhile, to wait for consensus to catch up :-)
I think that this change needs a WG Consensus Call, and some discussion with
area director.

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