<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: Quick question on a Request for package registration</TITLE>
</HEAD>
<BODY>
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">Dear all,</FONT>
</P>
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">As I've been involved in 3GPP working group discussions regarding these 3GPP H.248 extentions, I'd like to provide some additional information/comments.</FONT></P>
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">Although the 3GPP working groups view is that the 3GPP specification that contains the package definations in question is 95% complete. In my opinion these packages are not currently technically stable, during the last meeting the technical details for the encoding of the TFO package were not agreed.</FONT></P>
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">Additionally, there is the open issue within 3GPP as to whether these 3GPP H.248 specifications should be specified for both text and binary encodings, or whether only one encoding type should be chosen. </FONT></P>
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">However from reading clause 13.1 of H.248 (reproduced below) it seems that its a mandatory requirement to specify both a text and binary encoding of additional packages.</FONT></P>
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">13.1 Packages</FONT>
<BR><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">The following considerations SHALL be met to register a package with IANA:</FONT>
<BR><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">1) A unique string name, unique serial number and version number is registered for each package. The string name is used with text encoding. The serial number shall be used with binary encoding. Serial Numbers 60000-64565 are reserved for private use. Serial number 0 is reserved.</FONT></P>
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">..."</FONT>
</P>
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">Regards,</FONT>
</P>
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">Kevin.</FONT>
</P>
<BR>
<BR>
<BR>
<P><FONT SIZE=2 FACE="Tahoma">-----------------</FONT>
<BR><FONT SIZE=2 FACE="Tahoma">Kevin Gorey</FONT>
<BR><FONT SIZE=2 FACE="Tahoma">Nortel Networks, UMTS Strategic Product Planning</FONT>
<BR><FONT SIZE=2 FACE="Tahoma">Tel: +44 (0)1628 434606</FONT>
<BR><FONT SIZE=2 FACE="Tahoma">Fax: +44 (0)1628 434034</FONT>
<BR><FONT SIZE=2 FACE="Tahoma">kgorey@nortelnetworks.com</FONT>
</P>
<BR>
<UL>
<P><FONT SIZE=1 FACE="Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=1 FACE="Arial">From: </FONT></B> <FONT SIZE=1 FACE="Arial">ian.park@vf.vodafone.co.uk [SMTP:ian.park@vf.vodafone.co.uk]</FONT>
<BR><B><FONT SIZE=1 FACE="Arial">Sent: </FONT></B> <FONT SIZE=1 FACE="Arial">Wednesday, March 07, 2001 10:40 AM</FONT>
<BR><B><FONT SIZE=1 FACE="Arial">To: </FONT></B> <FONT SIZE=1 FACE="Arial">Taylor, Tom-PT [NORSE:B881:EXCH]; iana@iana.org</FONT>
<BR><B><FONT SIZE=1 FACE="Arial">Cc: </FONT></B> <FONT SIZE=1 FACE="Arial">megaco@fore.com; itu-sg16@mailbag.cps.intel.com; ian.park@vf.vodafone.co.uk</FONT>
<BR><B><FONT SIZE=1 FACE="Arial">Subject: </FONT></B> <FONT SIZE=1 FACE="Arial">RE: Quick question on a Request for package registration</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Dear all</FONT>
<BR><FONT SIZE=2 FACE="Arial"> </FONT>
<BR><FONT SIZE=2 FACE="Arial">FWIW, I agree entirely with Michelle's assessment. 3GPP specifications are</FONT>
<BR><FONT SIZE=2 FACE="Arial">*definitely* public documents (and we require that any document which is</FONT>
<BR><FONT SIZE=2 FACE="Arial">cited as a reference in a 3GPP specification is, in turn, a publicly</FONT>
<BR><FONT SIZE=2 FACE="Arial">available document).</FONT>
<BR><FONT SIZE=2 FACE="Arial"> </FONT>
<BR><FONT SIZE=2 FACE="Arial">On Tom Taylor's point about the stability of the specifications, we agreed</FONT>
<BR><FONT SIZE=2 FACE="Arial">at last week's working group meeting that the specifications are now ready</FONT>
<BR><FONT SIZE=2 FACE="Arial">for approval (which means that they will be brought under a formal change</FONT>
<BR><FONT SIZE=2 FACE="Arial">control system). They will be presented for approval at the meeting of</FONT>
<BR><FONT SIZE=2 FACE="Arial">Technical Specification Group Core network next week (14 - 16 March) in Palm</FONT>
<BR><FONT SIZE=2 FACE="Arial">Springs, CA.</FONT>
<BR><FONT SIZE=2 FACE="Arial"> </FONT>
<BR><FONT SIZE=2 FACE="Arial">I hope this helps.</FONT>
<BR><FONT SIZE=2 FACE="Arial"> </FONT>
<BR><FONT SIZE=2 FACE="Arial">Best regards</FONT>
<BR><FONT SIZE=2 FACE="Arial"> </FONT>
<BR><FONT SIZE=2 FACE="Arial">Ian Park</FONT>
<BR><FONT SIZE=2 FACE="Arial">___________________________________________________ </FONT>
<BR><FONT SIZE=2 FACE="Arial">Ian Park</FONT>
<BR><FONT SIZE=2 FACE="Arial">Chief Engineer, Core Network Signalling Standards</FONT>
<BR><FONT SIZE=2 FACE="Arial">Vodafone Limited</FONT>
<BR><FONT SIZE=2 FACE="Arial">*T: +44 1635 673 527 </FONT>
<BR><FONT SIZE=2 FACE="Arial">*F: +44 1635 233 562 </FONT>
<BR><FONT SIZE=2 FACE="Arial">?E: ian.park@vf.vodafone.co.uk </FONT>
<BR><FONT SIZE=2 FACE="Arial">___________________________________________________ </FONT>
<BR><FONT SIZE=2 FACE="Arial"> </FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">-----Original Message-----</FONT>
<BR><FONT SIZE=2 FACE="Arial">From: Tom-PT Taylor [<U></U></FONT><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial"><A HREF="mailto:taylor@nortelnetworks.com">mailto:taylor@nortelnetworks.com</A></FONT></U><FONT SIZE=2 FACE="Arial">]</FONT>
<BR><FONT SIZE=2 FACE="Arial">Sent: 26 February 2001 10:50</FONT>
<BR><FONT SIZE=2 FACE="Arial">To: IANA</FONT>
<BR><FONT SIZE=2 FACE="Arial">Cc: megaco@fore.com; itu-sg16@mailbag.intel.com; ian.park@vf.vodafone.co.uk</FONT>
<BR><FONT SIZE=2 FACE="Arial">Subject: RE: Quick question on a Request for package registration</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2 FACE="Arial">3GPP is a public forum, and I believe their packages would be viewed as</FONT>
<BR><FONT SIZE=2 FACE="Arial">public. I'll note that it is desirable that the packages be considered</FONT>
<BR><FONT SIZE=2 FACE="Arial">technically stable (though perhaps subject to some editing and minor</FONT>
<BR><FONT SIZE=2 FACE="Arial">adjustment) before they are registered.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">I've copied various parties for coordination purposes. </FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">> -----Original Message----- </FONT>
<BR><FONT SIZE=2 FACE="Arial">> From: IANA [</FONT><U> <FONT COLOR="#0000FF" SIZE=2 FACE="Arial"><A HREF="mailto:iana@iana.org">mailto:iana@iana.org</A></FONT></U><FONT SIZE=2 FACE="Arial"> <</FONT><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial"><A HREF="mailto:iana@iana.org">mailto:iana@iana.org</A></FONT></U><FONT SIZE=2 FACE="Arial">> ] </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Sent: Friday, February 23, 2001 5:28 PM </FONT>
<BR><FONT SIZE=2 FACE="Arial">> To: Taylor, Tom-PT [NORSE:B881:EXCH] </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Subject: FW: Quick question on a Request for package registration </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Tom, </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Quick question. Which range should these packages be registered in? </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Do I need to ask the applicants if these are public or private? </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> From the RFC: </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Public packages MUST be given serial numbers in the range 0x0001 to </FONT>
<BR><FONT SIZE=2 FACE="Arial">> 0x7fff. Private packages MUST be given serial numbers in the range </FONT>
<BR><FONT SIZE=2 FACE="Arial">> 0x8000 to 0xffff. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Thanks for any help. If there is someone better to ask, please let me </FONT>
<BR><FONT SIZE=2 FACE="Arial">> know. Don't want to bug you :) </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Michelle </FONT>
<BR><FONT SIZE=2 FACE="Arial">> IANA </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> ************************************************************** </FONT>
<BR><FONT SIZE=2 FACE="Arial">> *********** </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Hi there </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> I am the editor for a 3rd Generation Partnership Project </FONT>
<BR><FONT SIZE=2 FACE="Arial">> (3GPP) protocol </FONT>
<BR><FONT SIZE=2 FACE="Arial">> specification which defines extensions to the H.248/MeGaCo </FONT>
<BR><FONT SIZE=2 FACE="Arial">> protocol; I have </FONT>
<BR><FONT SIZE=2 FACE="Arial">> pasted in a copy of the "Scope" clause of this specification below. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> "The present document describes the protocol to be used on </FONT>
<BR><FONT SIZE=2 FACE="Arial">> the Media Gateway </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Controller (MGC) - Media Gateway (MGW) interface. The Media Gateway </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Controllers covered in this specification are the MSC server </FONT>
<BR><FONT SIZE=2 FACE="Arial">> and the GMSC </FONT>
<BR><FONT SIZE=2 FACE="Arial">> server. The basis for this protocol is the H.248/MEGACO protocol as </FONT>
<BR><FONT SIZE=2 FACE="Arial">> specified in ITU-T and IETF. The BICC architecture as </FONT>
<BR><FONT SIZE=2 FACE="Arial">> described in ITU-T </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Q.1902 [7]-[11] and 3G TS 23.205 [3] defines the usage of </FONT>
<BR><FONT SIZE=2 FACE="Arial">> this protocol. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> This specification describes the changes to H.248/MEGACO </FONT>
<BR><FONT SIZE=2 FACE="Arial">> which are needed to </FONT>
<BR><FONT SIZE=2 FACE="Arial">> handle 3GPP specific traffic cases. This is done by using the </FONT>
<BR><FONT SIZE=2 FACE="Arial">> H.248/MEGCO </FONT>
<BR><FONT SIZE=2 FACE="Arial">> standard extension mechanism. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> The present document is valid for a 3rd generation PLMN </FONT>
<BR><FONT SIZE=2 FACE="Arial">> (UMTS) complying </FONT>
<BR><FONT SIZE=2 FACE="Arial">> with Release 2000 and later. " </FONT>
<BR><FONT SIZE=2 FACE="Arial">> We need to define three new packages for this specification, </FONT>
<BR><FONT SIZE=2 FACE="Arial">> and as the </FONT>
<BR><FONT SIZE=2 FACE="Arial">> custodians of the package identifiers you are the people I </FONT>
<BR><FONT SIZE=2 FACE="Arial">> need to contact </FONT>
<BR><FONT SIZE=2 FACE="Arial">> to ask for the package numbers! </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> I have pasted in the first part of the definition of each </FONT>
<BR><FONT SIZE=2 FACE="Arial">> package below. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> 13.1.1 IuUP package. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> PackageID: 3giuup (0x####) </FONT>
<BR><FONT SIZE=2 FACE="Arial">> [Editor's note: PackageID to be allocated by IANA] </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Version: 1 </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Extends: None </FONT>
<BR><FONT SIZE=2 FACE="Arial">> This package identifies that the Iu User Plane is used for </FONT>
<BR><FONT SIZE=2 FACE="Arial">> the termination. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> It also contains some parameters for the Iu User Plane </FONT>
<BR><FONT SIZE=2 FACE="Arial">> functions in the MGW. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> The Iu User Plane is active in both directions independently </FONT>
<BR><FONT SIZE=2 FACE="Arial">> of the Stream </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Mode. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> 13.1.2 Circuit Switched Data package </FONT>
<BR><FONT SIZE=2 FACE="Arial">> PackageID: 3gcsd (0x####) </FONT>
<BR><FONT SIZE=2 FACE="Arial">> [Editor's note: PackageID to be allocated by IANA] </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Version: 1 </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Extends: None </FONT>
<BR><FONT SIZE=2 FACE="Arial">> This package contains the information needed to be able to </FONT>
<BR><FONT SIZE=2 FACE="Arial">> support GSM and </FONT>
<BR><FONT SIZE=2 FACE="Arial">> UMTS Circuit Switched Data from the media gateway. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> 13.1.3 TFO package </FONT>
<BR><FONT SIZE=2 FACE="Arial">> PackageID: 3gtfoc (0x####) </FONT>
<BR><FONT SIZE=2 FACE="Arial">> [Editor's note: PackageID to be allocated by IANA] </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Version: 1 </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Extends: None </FONT>
<BR><FONT SIZE=2 FACE="Arial">> This package defines events and properties for Tandem Free </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Operation (TFO) </FONT>
<BR><FONT SIZE=2 FACE="Arial">> control. TFO uses inband signalling and procedures for </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Transcoders to enable </FONT>
<BR><FONT SIZE=2 FACE="Arial">> compressed speech to be maintained between a tandem pair of </FONT>
<BR><FONT SIZE=2 FACE="Arial">> transcoders. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> This package allows an MGW which has inserted a transcoder to </FONT>
<BR><FONT SIZE=2 FACE="Arial">> support TFO. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Can you please let me know how I should go on from here to </FONT>
<BR><FONT SIZE=2 FACE="Arial">> have the package </FONT>
<BR><FONT SIZE=2 FACE="Arial">> numbers allocated? If you need any further information, </FONT>
<BR><FONT SIZE=2 FACE="Arial">> please contact me. </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Best regards </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Ian Park </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> ___________________________________________________ </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Ian Park </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Chief Engineer, Core Network Signalling Standards </FONT>
<BR><FONT SIZE=2 FACE="Arial">> Vodafone Limited </FONT>
<BR><FONT SIZE=2 FACE="Arial">> *T: +44 1635 673 527 </FONT>
<BR><FONT SIZE=2 FACE="Arial">> *F: +44 1635 233 562 </FONT>
<BR><FONT SIZE=2 FACE="Arial">> *E: ian.park@vf.vodafone.co.uk </FONT>
<BR><FONT SIZE=2 FACE="Arial">> ___________________________________________________ </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
<BR><FONT SIZE=2 FACE="Arial">> </FONT>
</P>
</UL>
</BODY>
</HTML>