Subject: [dispatch] https://www.ietf.org/id/draft-dawes-sipcore-mediasec-parameter-03.txt

From: "Dawes, Peter, Vodafone Group" <[email-masked]>
Date: Wed, 10 Feb 2016 11:32:58 +0000

Hello All,
I would like to ask dispatch to (re-)consider the proposals in https://datatracker.ietf.org/doc/draft-dawes-sipcore-mediasec-parameter/ and how it might be progressed. One of the sipcore chairs has indicated that this draft probably does not belong in sipcore and dispatch did not make a detailed evaluation the first time it was brought to the group. 

The most recent comments on the sipcore mailing list are https://mailarchive.ietf.org/arch/msg/sipcore/mD1Qedh93ep9oVOxttIxKN7lIcg and it might help to repeat part of what I said there about the new header field parameter that is the reason for the draft: 

"...the header field parameter introduced by this draft originates from 3GPP specifications and related procedures and header field values are also described in 3GPP specifications. The purpose of this draft is to name the header field parameter, give several illustrative examples to make it clear how it is used, and set up an IANA registry for existing and future values. The draft does not propose that IETF defines any new security setup procedures, ciphering, integrity protection etc."

Thanks and regards,
Peter