vcard value types

Hi.

RFC 2426 (http://www.ietf.org/rfc/rfc2426.txt)
in Sec 2.4.2 defines the "vcard" value type.  This is used for encoding
a separate vcard into a value within an enclosing vcard.

That section includes the example:

AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n
 TITLE:Area Administrator\, Assistant\n EMAIL\;TYPE=INTERN\n
 ET:[email protected]\nEND:VCARD\n

Of note, section 2.6 also says:
"Specifically, when parsing a content line, folded lines must first be
unfolded according to the unfolding procedure described in [MIME-DIR]."
and "Unfolding is done before any decoding of a type value in a content
line."

So, after *first* applying RFC2425 Sec 5.8.1 'Line delimiting and
folding' I would expect the above example to be transformed into the
following single unfolded line:

AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\nTITLE:Area Administrator\, Assistant\n EMAIL\;TYPE=INTERN\nET:[email protected]\nEND:VCARD\n

To which I would *then* decode to:

AGENT:BEGIN:VCARD
FN:Joe Friday
TEL:+1-919-555-7878
TITLE:Area Administrator, Assistant
 EMAIL;TYPE=INTERN
ET:[email protected]
END:VCARD

Now, this to me is apparently invalid data (?).  I would think that:

1) the space should be removed before 'EMAIL'?
2) the '\n' in 'INTERNET' should be removed?
3) the ':' characters in 'BEGIN:VCARD' and 'END:VCARD' should also be
escaped with backslashes when encoded?

So, my question is, is the example indeed incorrect, and if so, in which
of those three ways, or am I missing something?

Much Thanks.

-- 
Chris Hubick
mailto:[email protected]
mailto:[email protected]
phone:1-780-421-2533 (work)
phone:1-780-721-9932 (cell)
http://www.hubick.com/


__ 
    This communication is intended for the use of the recipient to whom it
    is addressed, and may contain confidential, personal, and or privileged
    information. Please contact us immediately if you are not the intended
    recipient of this communication, and do not copy, distribute, or take
    action relying on it. Any communications received in error, or
    subsequent reply, should be deleted or destroyed.
---