[BEEPwg] Underspecifications in RFC 3080? (profile content, SWS avoidance)

Marshall T. Rose mrose+mtr.netnews@dbc.mtview.ca.us
Tue, 30 Oct 2001 09:33:57 -0800


> I wrote:
> > As far as the profile is concerned, the initialization element is a
> > bucket of octets.  The profile gets to decide how they are
> > interpreted.  See RFC 3080 section 2.2.2.
>
> And of course, that doesn't make sense, since the initialization
> element might not be base64-encoded, in which case it comes as
> characters, not bytes.

we can certainly update the spec, though i'd like to see a concrete proposal
as to what the change is.

perhaps a good solution is to add a new value for the encoding attribute
that specifies that the piggyback is a MIME object that has been encoded
(headers and all) with base64.

for myself, the model i currently use is to undo the base64, if any, and
then pass the piggyback as application/octet-stream to the profile engine...

/mtr