datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Liaison Statement: OMA LS 166 Liaison Statement to the IETF Requesting Guidance on using LCT revised

Submission Date: 2007-02-15
From: OMA (Dean Willis)
To: IETF Reliable Multicast Transport (RMT) Working Group (adamson@itd.nrl.navy.mil, lorenzo@vicisano.net)
Cc:magnus.westerlund@ericsson.com
lars.eggert@nokia.com
rmt@ietf.org
Response Contact: Toni Paila
Technical Contact: Toni Paila
Purpose: For action
Deadline: 2007-03-23 Action Taken
Attachments: PDF of liaison statement
Body:
1	Overview

OMA BAC-BCAST has a question to IETF RMT on the stability of
standards-track evolution of 'Layered Coding Transport (LCT) Building
Block'. The latest Internet-Draft revision -04 (expired) of LCT
introduced the header extension EXT_TIME for the purpose of signalling
time stamps of different nature. OMA BAC-BCAST would be interested to
use that method but is hesitant to refer to ongoing IETF work unless
such work can be considered stable. Our concrete questions are: 

1.	Does IETF RMT consider the revision of LCT building block stable
enough so that we can refer to that in OMA BCAST 1.0 specification?

2.	What is estimated schedule for revising the RMT RFCs on the
Standards Track?

2	Requested Action(s)
OMA BAC-BCAST requests IETF RMT to provide guidance on the two
questions presented in this liaison.

3	Conclusion


We thank you for your consideration.

With best regards, 
OMA BAC BCAST 
(Mobile Broadcast Services sub working group)