22
IEEE 1722 AVB L2 Transport Protocol Dave Olsen [email protected] 4/6/10 IEEE 1722 Face-to-Face Berkeley, California 1
IEEE 1722AVB L2 Transport Protocol
Dave [email protected]
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
1
Face-to-Face AgendaFace to Face Agenda
• Administrivia• Sponsor Ballot Status
– Par Modifications– Policies and Procedures– Assigned Numbers
• Draft 2.2 Review• New Work
– 1722 over IP– Media Clock Negotiation– MJPEG support– Support of MIME types over 1722
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
2
The IEEE-SA strongly recommends that at each WG meeting the chair or a designee:
Instructions for the WG Chairg
Show slides #1 through #4 of this presentationAdvise the WG attendees that:
The IEEE’s patent policy is consistent with the ANSI patent policy and is described in Clause 6 of the IEEE-SA Standards Board Bylaws;E l id tifi ti f t t l i hi h b ti l f th f t d d dEarly identification of patent claims which may be essential for the use of standards under development is strongly encouraged; There may be Essential Patent Claims of which the IEEE is not aware. Additionally, neither the IEEE, the WG, nor the WG chair can ensure the accuracy or completeness of any assurance or whether any such assurance is, in fact, of a Patent Claim that is essential for the use of the standard under developmentstandard under development.
Instruct the WG Secretary to record in the minutes of the relevant WG meeting:That the foregoing information was provided and that slides 1 through 4 (and this slide 0, if applicable) were shown; That the chair or designee provided an opportunity for participants to identify patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent applicationclaim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) of which the participant is personally aware and that may be essential for the use of that standard Any responses that were given, specifically the patent claim(s)/patent application claim(s) and/or the holder of the patent claim(s)/patent application claim(s) that were identified (if any) and by whom.and by whom.
The WG Chair shall ensure that a request is made to any identified holders of potential essential patent claim(s) to complete and submit a Letter of Assurance.It is recommended that the WG chair review the guidance in IEEE-SA Standards Board Operations Manual 6.3.5 and in FAQs 12 and 12a on inclusion of potential Essential Patent Claims by incorporation or by reference
25 March 2008
incorporation or by reference.
Note: WG includes Working Groups, Task Groups, and other standards-developing committees with a PAR approved by the IEEE-SA Standards Board.
(Optional to be shown)
Participants, Patents, and Duty to Inform
All ti i t i thi ti h t i bli ti d th IEEE SAAll participants in this meeting have certain obligations under the IEEE-SA Patent Policy. Participants:
“Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents
“Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents or patent claims
“Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents)The above does not apply if the patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) p pp p p ( )under consideration by this group
Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2Early identification of holders of potential Essential Patent Claims is strongly encouraged
25 March 2008
encouragedNo duty to perform a patent search
Slide #1
Patent Related LinksAll participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development.Patent Policy is stated in these sources:
IEEE SA Standards Boards BylawsIEEE-SA Standards Boards Bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3
Material about the patent policy is available athttp://standards ieee org/board/pat/pat material htmlhttp://standards.ieee.org/board/pat/pat-material.html
If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at [email protected] or visit http://standards.ieee.org/board/pat/index.html
25 March 2008Slide #2
This slide set is available at http://standards.ieee.org/board/pat/pat-slideset.ppt
Call for Potentially Essential PatentsCall for Potentially Essential Patents
If anyone in this meeting is personally awareIf anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the p y pproposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance:
Either speak up now orProvide the chair of this group with the identity of theProvide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible orCause an LOA to be submitted
25 March 2008Slide #3
Other Guidelines for IEEE WG MeetingsMeetings
All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws.
Don’t discuss the interpretation validity or essentiality of patents/patentDon t discuss the interpretation, validity, or essentiality of patents/patent claims. Don’t discuss specific license rates, terms, or conditions.
Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetingsapproaches may be discussed in standards development meetings.
Technical considerations remain primary focus
Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets.Don’t discuss the status or substance of ongoing or threatened litigation.Don’t be silent if inappropriate topics are discussed … do formally object.
---------------------------------------------------------------See IEEE SA Standards Board Operations Manual clause 5 3 10 and “Promoting Competition and Innovation:See IEEE-SA Standards Board Operations Manual, clause 5.3.10 and “Promoting Competition and Innovation:
What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details.
25 March 2008Slide #4
Website & ReflectorWebsite & Reflector
• http://grouper ieee org/groups/1722/http://grouper.ieee.org/groups/1722/– SFTP upload and Private Area available
To subscribe to the p1722 reflector email• To subscribe to the p1722 reflector, email [email protected]
fwith the following text in the body:subscribe avbtp <yourFirstName> <yourLastName>
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
8
Sponsor BallotSponsor Ballot
• Sponsor Ballot closes April 30 2010Sponsor Ballot closes April 30 2010 • Vote early and often
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
9
PAR ModificationsPAR Modifications
• 5.2 Scope: This standard specifies the protocol, data encapsulations, connection management and presentation time procedures used to ensure interoperability between audio and video based end stations that use standard networking services provided by all IEEE 802 networks meeting QoS requirements for time-sensitive applications by leveraging concepts ofQoS requirements for time sensitive applications by leveraging concepts of IEC 618831-7.
• 5.2 Scope: This standard specifies the protocol, data encapsulations, p p p , p ,connection management and presentation time procedures used to ensure interoperability between audio and video based end stations that use standard networking services provided by all IEEE 802 networks meeting QoS requirements for time sensitive applications by leveraging concepts ofQoS requirements for time-sensitive applications by leveraging concepts of IEC 618831-8.
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
10
IEEE 1722 Policies and ProceduresIEEE 1722 Policies and Procedures
• 9.3 Actions Requiring Approval by two-thirds vote q g pp yThe following actions require approval by two-thirds vote:
a) Approval of change of the working group scope b) Approval to move the draft standards project to the
Sponsor for IEEE Standards Sponsor ballotSponsor for IEEE Standards Sponsor ballot
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
11
MotionMotion
• Motion: Approve the changes to the IEEEMotion: Approve the changes to the IEEE 1722 PAR to include 61883-8 in the scope of the projectof the project.
• ForA i t• Against
• Abstain- Approved by Acclamation
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
12
Draft ReviewDraft Review
• Current draft: IEEE P1722™/D2 2Current draft: IEEE P1722 /D2.2
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
13
New WorkNew Work
• 1722 over IP1722 over IP• Media Clock Negotiation
MJPEG t• MJPEG support• Support of MIME types over 1722
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
14
1722 over IP1722 over IP
• Advantages:Advantages:– Fits universally established networking model– Allows applications running on Linux and other OS’esAllows applications running on Linux and other OS es
to gain access to AVB services (without have to resort to Raw Sockets)C tibilit ith t h d i l t ti– Compatibility with current hardware implementations
– Simpler that RTP • Fixed data offset• Fixed data offset• Single packet type
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
15
1722 over IP1722 over IP
• Disadvantages:Disadvantages:– More header overhead
UDP checksum– UDP checksum– Multicast environment needs to be defined
Complicates implementations to detect– Complicates implementations to detect versions
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
16
1722 over IP1722 over IP
IP Header
1722 Payload
1722 Header
UDP Header
• IPv4 header – 20 bytes• IPv6 header – 40 bytesy• UDP header – 8 bytes
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
17
Media Clock NegotiationMedia Clock Negotiation
• Automatic configuration of media clocksAutomatic configuration of media clocks• No user intervention to select a media
clock masterclock master• Multiple rates• Automatic failover
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
18
MJPEG supportMJPEG support
• Immediate need to support MJPEGImmediate need to support MJPEG• 61883-4 transport stream
61883 8 f t• 61883-8 new format• ITU work underway to define MJPEG over
transport stream• RFC 3550 format for MJPEG over RTP
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
19
MIME typesMIME types
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
20
MIME types
Table 5.2 – AVBTP subtype values
MIME types
Hexadecimal Value FUNCTION Meaning
00 61883 C S C 61883/ C A l0016 61883_IIDC_SUBTYPE IEC 61883/IIDC over AVBTP protocol
0116 MMA_SUBTYPE MMA payload over AVBTP protocol
0216 MIME_SUBTYPE MIME payload over AVBTP protocol
0316-7D16 - Reserved for future protocols0316 7D16 Reserved for future protocols
7E16 MAAP MAAP Protocol Packet
7F16 EXPERIMENTAL SUBTYPE Experimental over AVBTP
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
21
Next StepsNext Steps
• Amend current PARAmend current PAR• Complete Sponsor Ballot
D ft PAR f k• Draft PAR for new work
4/6/10 IEEE 1722 Face-to-FaceBerkeley, California
22
