We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byJacquelyn Swafford
Modified about 1 year ago
Copyright © 2003 Colin Perkins SDP Specification Update Colin Perkins
Copyright © 2003 Colin Perkins Status draft-ietf-mmusic-sdp-new-13 submitted in late May –Attempt to clarify when it is appropriate to use " k= " –Deprecate unregistered " X- " attributes and media formats Descriptive text and IANA Considerations sections were inconsistent previously –Clarify that RTP can use non-contiguous ports To match changes in RTP specification since RFC 1889 –Clarify that " a=charset " is a session level attribute –Edit IANA Considerations text for clarity –Update references A few minor comments on the mailing list IESG review found a number of issues –Full set sent to the mailing list yesterday –Looking for input today…
Copyright © 2003 Colin Perkins Issues raised on the mailing list (1) Inconsistency between ABNF definition of token-char and the comment following it (Pekka Pessi) –Affects " m= ", " a= ", " k= ", " c= " and " b= " lines Two options: 1.Leave ABNF as-is, and change the comment 2.Update the ABNF for token-char, making the following legal: 0x22 0x2f 0x3d 0x3f 0x5b 0x5d 0x5c " / = ? [ ] \ Opinions from implementers?
Copyright © 2003 Colin Perkins Issues raised on the mailing list (2) Clarify use of " b= " with layered coding (Belling Thomas) For the CT modifier add: For RTP, if several RTP sessions are part of the conference, the conference total refers to total bandwidth of all RTP sessions. Accept?
Copyright © 2003 Colin Perkins Issues raised on the mailing list (3) Clarify which ports are associated with which " m= " line, with layered coding (Belling Thomas). In the definition of " m= " change: For RTP, the default is that only the even numbered ports are used for data and the corresponding one- higher odd port is used for the RTCP belonging to this RTP session, and the denotes the number of RTP sessions. Accept
Copyright © 2003 Colin Perkins IESG comments (1) The " k= " field is under-specified Should it be deprecated and/or replaced by the work in sdescriptions or key-mgmt? Opinions from implementers?
Copyright © 2003 Colin Perkins IESG comments (2) Specify that, when using " k= ": "ensure that the secure channel is with the party that is authorized to join the session, not an intermediary" "If a caching server is used, there ought to be a way to keep the server from accessing the key" Good points, need to be specified by users of SDP?
Copyright © 2003 Colin Perkins IESG comments (3) Regarding " k= ": "Also, it is generally a good idea to indicate the algorithm that a cryptographic key is intended to support. I suggest that the encryption key type be revised to specify the key as well as the algorithm that the key will be used with." Implied by the URI reference or media protocol "Finally, many security protocols require two keys, one for confidentiality and another for integrity. This specification does not support the transfer of two keys." use sdescriptions or key-mgmt if this is important
Copyright © 2003 Colin Perkins IESG comments (4) Two suggested additions to " k= ": "name the key without actually including the key. In PEM (see RFC 1040), the Recipient-ID was used to name key- encryption keys, and a similar scheme could be employed here." "would be nice to encrypt the session key in a key that is not included in SDP. PEM also includes a mechanism for wrapped symmetric keys." Use sdescriptions or key-mgmt if this is important
Copyright © 2003 Colin Perkins IESG comments (5) In security considerations: SHOULD NOT automatically drop you into an interactive session MUST NOT Accept
Copyright © 2003 Colin Perkins IESG comments (6) Regarding " c= ": Just as a query, has anyone considered using a specific marker of private address realms for SDP? That is, using a network type other than IN to indicate that the domain name or address given are not globally unique/globally reachable? Reject; Interesting, but not backwards compatible
Copyright © 2003 Colin Perkins IESG comments (7) "The text on internationalisation says UTF-8 only applies to informational fields. Does this mean it isn't required to perform any normalization whatsoever on the UTF-8? Would it make sense to explicitly state that normalization isn't needed." Seek clarification…
Copyright © 2003 Colin Perkins IESG comments (8) For " a=inactive " It was suggested apps use something like "sdp.inactive" so that the.inactive TLD could reinforce the a=inactive flag. In that instance, would the presence of that TLD be a condition under which the RTCP SHOULD is appropriately not done, and no RTCP sent? If so, is mentioning that case appropriate here?" Note that it might be appropriate to set the " c= " line for inactive media to indicate no transport address. Specify in the users of SDP?
Copyright © 2003 Colin Perkins IESG comments (9) The "u=" and " k= " lines assume the that the URI can be de-referenced. This is not always the case; so we may need to explicitly state the assumption The URI for " k= " only makes sense for particular types of URI. Might give guidance that this is typically an http or https URI? Accept both
Copyright © 2003 Colin Perkins The way forward Summarise these slides and discussion to the list… Incorporate comments into a –14 revision in the next couple of weeks – please give feedback! Discuss with IESG and resubmit…
Re-INVITE Handling draft-camarillo-sipping-reinvite-00.txt
1/24/2005CTS II - HL7 Vocabulary TC CTS II HL7 Working Group Meeting Vocabulary TC.
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec Title: Security TG Call For Proposals Date Submitted: March 11, 2009 Presented at IEEE
Bristol Year 12 Conference Answering Data Response Questions John Birchall.
1 Computer Networks: A Systems Approach, 5e Larry L. Peterson and Bruce S. Davie Chapter 9 Applications Copyright © 2010, Elsevier Inc. All rights Reserved.
Session Management in Web Applications Author: EUROSEC GmbH Chiffriertechnik & Sicherheit Tel: / 60850, © EUROSEC GmbH Chiffriertechnik.
TITRE 4 th REMIT IT Expert Group Ljubljana, 27 th June 2013 Discussion on ACER Guidelines for RRM and RIS Stefano Bracco Knowledge Manager.
EHR-S Reconciliation Worksheet Instructions. The spreadsheet is an extract from the EHR-S Database. Each column is Filterable by click- ing on the header.
LIS901N lecture 5: http URI and apache Thomas Krichel
Security attacks. - confidentiality: only authorized parties have read access to information - integrity: only authorized parties have write access to.
Doc: IEEE 802/xxx DRAFT UNAPPROVED DRAFTIEEE 802 LMSCSlide 1 September 2006 IEEE 802 LMSC recommendation to ISO/IEC JTC1/SC6 for the review of &
StaffShare Limited is a Social Enterprise Company WELCOME © Copyright StaffShare Limited December 2010 StaffShare and The Skill Exchange are registered.
Linked Lists. Please Read These slides are provided for the use of students enrolled in James Durbanos Data Structures class (CISC 220). They are the.
es IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Response to ES PAR and 5C Comments Date Submitted: March,
Advanced NIMAC 2.0 for AUs: The Watchlist, Contact Information, and User Information Features 1www.nimac.us.
IETF 71 SIPPING WG meeting draft-ietf-sipping-pai-update-00.
Cookies, Sessions. Server Side Includes You can insert the content of one file into another file before the server executes it, with the require() function.
The Centralized Performance System Medical Module CPS Basics.
Compiled by : S. Agarwal Lecturer & Systems Incharge St. Xaviers Computer Centre St. Xaviers College, Kolkata. INTERNET PROTOCOLS.
Doc.: ec INTL Submission to SC6 January 2014 IEEE 802Slide 1 IEEE 802 Response to FDIS comments on IEEE 802.1AE and IEEE 802.1X 16 January 2014.
PowerPoint Presentation: Richard H. Baum, Ph.D. DeVry Institute of Technology 9th Edition Nancy Stern Hofstra University Robert A. Stern Nassau Community.
Course Outline: System Requirements What is Vi Editor
Submission doc.: IEEE 11-13/ ak-r0 March 2013 Norman Finn, Cisco SystemsSlide 1 Changes to 802.1Q required by 802.1Qbz Date: Authors:
Lord Mandelson of Foy and Hartlepool is a descendant of which Labour leader? 1.Harold Wilson 2.George Brown 3.Gordon Brown 4.Herbert Morrison 5.Clement.
MSc IT UFCE8K-15-M Data Management Prakash Chatterjee Room 2Q18
SIP WG Open Issues Jonathan Rosenberg. Record-Routing Problem: spec omits anything about Routing in reverse direction Lots and lots and lots of discussion.
Network Security Protecting An Organizations Network.
Using the STARS-SES Provider Annual Reporting System (PARS) Illinois State Board of Education.
Welcome to SuperFleet Manager Taking your fleet fueling to the next level.
© 2016 SlidePlayer.com Inc. All rights reserved.