Re: [pcp] I-D ACTION:draft-ietf-pcp-description-option-05.txt

Section 3 of this draft seems to hint at different forms of option
processing compared to what is defined in RFC 6887.

If the PCP client includes the DESCRIPTION option and marks it as
mandatory the PCP server should return UNSUPP_OPTION if it does not
support it, rather than ignore it. In fact, if it truly doesn't
understand this option, that's what it will do anyway; you would have
to teach the server about this option to then make it ignore it. RFC
6887 defines the method of marking options as optional so clients
should use that if they don't want the option to potentially trigger an
error response from the server.

If the PCP client includes malformed UTF-8 content then the PCP server
should return MALFORMED_OPTION as per the standard option processing
rather than just ignore the option/request.

Matt

* Internet-Drafts@ietf.org <Internet-Drafts@ietf.org> [2014-02-21 12:10:39]:
> A new Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Port Control Protocol Working Group of the IETF.
> 
>     Title         : PCP Description Option
>     Author(s)     : M. Boucadair, et al
>     Filename      : draft-ietf-pcp-description-option
>     Pages         : 6 
>     Date          : 2014-02-21 
>     
> This document extends Port Control Protocol (PCP) with the ability to
>    associate a description with a PCP-instantiated mapping.  It does so
>    by defining a new DESCRIPTION option.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pcp-description-option-05.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.

> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp