idnits 2.17.1 draft-camarillo-sipping-message-tag-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 173. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 150. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 157. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 163. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 1, 2005) is 6897 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2327 (ref. '1') (Obsoleted by RFC 4566) == Outdated reference: A later version (-26) exists of draft-ietf-mmusic-sdp-new-24 Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SIPPING Working Group G. Camarillo 3 Internet-Draft Ericsson 4 Expires: December 3, 2005 June 1, 2005 6 Internet Assigned Number Authority (IANA) Registration of the Message 7 Media Feature Tag 8 draft-camarillo-sipping-message-tag-00.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on December 3, 2005. 35 Copyright Notice 37 Copyright (C) The Internet Society (2005). 39 Abstract 41 This document registers with the IANA a new media feature tag 42 associated with the 'message' media type. This media feature tag 43 indicates that a particular device supports 'message' as a streaming 44 media type. Media feature tags can be used to route calls to devices 45 that support certain features. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. Security Considerations . . . . . . . . . . . . . . . . . . . 3 51 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 52 4. Acknowledges . . . . . . . . . . . . . . . . . . . . . . . . . 4 53 5. Normative References . . . . . . . . . . . . . . . . . . . . . 4 54 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 4 55 Intellectual Property and Copyright Statements . . . . . . . . 5 57 1. Introduction 59 The SDP (Session Description Protocol) specification [5] defines a 60 number of media types. RFC 3840 [4] registers with the IANA media 61 feature tags associated with all those media types except for the 62 'message' media type. This document registers a new media feature 63 tag that is associated with the 'message' media type. 65 The reason why the 'message' media feature tag was not registered by 66 RFC 3840 was that when RFC 3840 was published, the SDP specification 67 was RFC 2327 [1]. RFC 3840 defined media feature tags for all the 68 media types defined by RFC 2327. However, RFC 2327 did not define 69 the 'message' media type. This media type was defined by the revised 70 SDP specification [5], which was published after RFC 3840. 72 2. Security Considerations 74 This specification does not affect the security of the Internet. RFC 75 3840 [4] discusses security considerations related to the use of 76 media feature tags. 78 3. IANA Considerations 80 This specification registers a new media feature tag in the SIP [3] 81 tree per the procedures defined in RFC 2506 [2] and RFC 3840 [4]. 83 Media feature tag name: sip.message 85 ASN.1 Identifier: New assignment by IANA. 87 Summary of the media feature indicated by this tag: This feature 88 tag indicates that the device supports message as a streaming 89 media type. 91 Values appropriate for use with this feature tag: Boolean. 93 The feature tag is intended primarily for use in the following 94 applications, protocols, services, or negotiation mechanisms: This 95 feature tag is most useful in a communications application for 96 describing the capabilities of a device, such as a phone or PDA. 98 Examples of typical use: Routing a call to a phone that can 99 support session-based instant messaging. 101 Related standards or documents: RFC xxxx. (Note for the RFC 102 editor: substitute xxxx with the number of this RFC) 104 Security Considerations: Security considerations for this media 105 feature tag are discussed in Section 11.1 of RFC 3840. 107 4. Acknowledges 109 The need for this registration was discussed with Jonathan Rosenberg, 110 Colin Perkins, and Jon Peterson. 112 5. Normative References 114 [1] Handley, M. and V. Jacobson, "SDP: Session Description 115 Protocol", RFC 2327, April 1998. 117 [2] Holtman, K., Mutz, A., and T. Hardie, "Media Feature Tag 118 Registration Procedure", BCP 31, RFC 2506, March 1999. 120 [3] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., 121 Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: 122 Session Initiation Protocol", RFC 3261, June 2002. 124 [4] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Indicating User 125 Agent Capabilities in the Session Initiation Protocol (SIP)", 126 RFC 3840, August 2004. 128 [5] Handley, M., "SDP: Session Description Protocol", 129 draft-ietf-mmusic-sdp-new-24 (work in progress), February 2005. 131 Author's Address 133 Gonzalo Camarillo 134 Ericsson 135 Hirsalantie 11 136 Jorvas 02420 137 Finland 139 Email: Gonzalo.Camarillo@ericsson.com 141 Intellectual Property Statement 143 The IETF takes no position regarding the validity or scope of any 144 Intellectual Property Rights or other rights that might be claimed to 145 pertain to the implementation or use of the technology described in 146 this document or the extent to which any license under such rights 147 might or might not be available; nor does it represent that it has 148 made any independent effort to identify any such rights. Information 149 on the procedures with respect to rights in RFC documents can be 150 found in BCP 78 and BCP 79. 152 Copies of IPR disclosures made to the IETF Secretariat and any 153 assurances of licenses to be made available, or the result of an 154 attempt made to obtain a general license or permission for the use of 155 such proprietary rights by implementers or users of this 156 specification can be obtained from the IETF on-line IPR repository at 157 http://www.ietf.org/ipr. 159 The IETF invites any interested party to bring to its attention any 160 copyrights, patents or patent applications, or other proprietary 161 rights that may cover technology that may be required to implement 162 this standard. Please address the information to the IETF at 163 ietf-ipr@ietf.org. 165 Disclaimer of Validity 167 This document and the information contained herein are provided on an 168 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 169 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 170 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 171 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 172 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 173 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 175 Copyright Statement 177 Copyright (C) The Internet Society (2005). This document is subject 178 to the rights, licenses and restrictions contained in BCP 78, and 179 except as set forth therein, the authors retain all their rights. 181 Acknowledgment 183 Funding for the RFC Editor function is currently provided by the 184 Internet Society.