megaco ip phone status peter blatherwick12.5.001tia tr-41.3.4, may 2000 meeting megaco ip phone...

Megaco IP Phone Status Peter Blatherwick 12.5.001

TIA TR-41.3.4, May 2000 Meeting

Megaco IP Phone Standards Status Update

Peter BlatherwickNortel Networks, on behalf of TIA TR-41.3.4



Megaco IP Phone Standards - Status Overview

IETF, Megaco WG

ITU – T, SG-16

TIA, TR-41.3.4 WG

H.248 Annex G

Gateway Control Protocol(IDENTICAL to Megaco Protocol)

User Interface Packages(= Megaco IP Phone Pkgs subset)

Generic Packages(Megaco WG core documents)• Application-specific content

“packages”• Includes IP Phone User Interface

elements and many others

Megaco IP Phone• Application-specific document• Broad master/slave control architecture for IP

Phone and similar appliances• Specific package usage (reference)• IP Phone protocol profile (select from options)

VoIP Telephone (PN 4462)• Soup-to-nuts “whole device” standard• Includes options for Megaco, SIP &

H.323 control• Specific constraints for business

telephones

Megaco Protocol(Megaco WG core document)• Gateway control architecture• Syntax and message format• Package and profile rules• Options for transport & encoding

reference reference

references

clone clone

SIP, H.323, audio, Ethernet, power, safety ...

Complete• All issues addressed• Moving to TIA Interim Std

In Progress, Nearing Final• Technically solid, all dependencies done• Proceeding to Informational RFC (IETF

47 decision, Mar 00)• Minor issues and re-post in progress

Pending Process• User Interface Packages

to move to Standards Track RFC when decided in ITU (June 00?)

Complete• Determined, Feb 00• Minor updates submitted for

May 00 mtng, Osaka• Expected to move to

Recommendation in June

Complete• Last Call, passed May 00• Will move to Proposed Std

RFC imminently, pending ITU process & synch-up

Complete• ITU SG-16 meeting, May

00, Osaka, expected to pass determined text

• Process & synch-up agreed



Recent Events and ProgressMegaco IP Phone Specification:

• draft-ietf-megaco-ipphone-02.txt, 4th revision I-D posted to Megaco WG, 29.03.00• Changes:

– Specific User Interface termination defined, not ROOT termination (accommodates list issues)– Specific selections on transport and encoding options in Megaco/H.248 (UDP/ALF and Text)– Restructured to define an application profile, alignment with latest Megaco/H.248 and Packages

• IETF last call readiness: – Technically very solid, small number of issues remain, all well understood (see Issues next)– All dependencies in place (finally!)– Pretty much ready to rock!

IETF 47, Mar 00 Decisions:• Megaco IP Phone may proceed to Informational RFC – big progress• ITU-defined package sets (incl. User Interface set from Megaco IP Phone) will move to

IETF RFCs in parallel process – big progress• Megaco IP Phone protocol subset profile not accepted (See Issues, next)

ITU-T SG-16:• H.248 Annex G: User Interface Packages well accepted, expected to pass to

Recommendation with no major issues, as part of larger “starter kit” – big progress• Annex G Update re minor issues for Megaco IP Phone submitted, May 00, Osaka

meeting, no issues anticipated (see Issues, next)• Proposed for SG-16 to use Annex G User Interface Packages as part of H.323/Stimulus

as well (status unclear)



Issues, In ProgressMegaco IP Phone specification:

• Need to define naming conventions for audio and user interface terminations, to allow efficient audit and capabilities discovery

– Proposal: define well known termination names, audit using wildcard

H.248 Annex G User Interface Packages:• Keypad tone feedback

– Proposal: add property to Keypad Package, to direct tone feedback to audio transducer or RTP termination

• Keypad display feedback– Proposal: add property to Keypad Package, to direct characters to display

• Digit map completion event during keypad dialling– Proposal: define completion event in Keypad Package

• Note: Annex G Update with above proposals submitted to ITU SG-16

Subset protocol issue:• Protocol subset profile not accepted in Megaco WG, IETF 47 meeting

– Unfortunately, had to be negotiated away in order to progress the Megaco IP Phone document, not avoidable

– Not absolutely critical to success, but a very useful optimisation (adds some unnecessary overhead)

– Option to make subset profiling a TIA requirement and/or try again later in Megaco Protocol version 2 (prefer the latter)

• Strongly recommend TR-41.3.4 proceed now without subset profile rather than fight (and lose) in IETF



Next Steps1. Finalize Annex G User Interface Packages

• Updates submitted for SG-16 meeting, May 15-19, 2000, Osaka• Deal with any issues from meeting (nothing major anticipated)

2. Re-submit Megaco IP Phone specification, final I-D for Last Call• Minor issues proposal in progress• Editorial changes for IETF 47 comments, remove subset profile• Post to TR-41.3.4 e-mail list for final comment (rapid turnaround)

3. IETF Last Call Process for Megaco IP Phone specification• Last Call, Megaco WG level (Tom Taylor / Chair to call, pending step 2)

• Last Call, IETF level (Tom Taylor to recommend to IESG, pending Megaco last call results)

• Any issues to be dealt with on Megaco list

4. Megaco IP Phone RFC Publication• Submit final to RFC Editor for publication as Informational RFC, based on IESG

decision from IETF level Last Call

• Hopefully, completed and published by mid-summer 2000

megaco ip phone status peter blatherwick12.5.001tia tr-41.3.4, may 2000 meeting megaco ip phone...

Documents