<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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 SIZE=2>Not having been involved in the 3GPP work I was not aware of the 3 new packages referred to in the initial email.</FONT>
</P>
<P><FONT SIZE=2>Could someone provide info on where to obtain copies of these packages?</FONT>
</P>
<P><FONT SIZE=2>Thanks,</FONT>
</P>
<P><FONT SIZE=2>Michael Brown</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: ian.park@vf.vodafone.co.uk [<A HREF="mailto:ian.park@vf.vodafone.co.uk">mailto:ian.park@vf.vodafone.co.uk</A>]</FONT>
<BR><FONT SIZE=2>Sent: Wednesday, March 07, 2001 5:40 AM</FONT>
<BR><FONT SIZE=2>To: Taylor, Tom-PT [NORSE:B881:EXCH]; iana@iana.org</FONT>
<BR><FONT SIZE=2>Cc: megaco@fore.com; itu-sg16@mailbag.cps.intel.com;</FONT>
<BR><FONT SIZE=2>ian.park@vf.vodafone.co.uk</FONT>
<BR><FONT SIZE=2>Subject: RE: Quick question on a Request for package registration</FONT>
</P>
<BR>
<P><FONT SIZE=2>Dear all</FONT>
<BR><FONT SIZE=2> </FONT>
<BR><FONT SIZE=2>FWIW, I agree entirely with Michelle's assessment. 3GPP specifications are</FONT>
<BR><FONT SIZE=2>*definitely* public documents (and we require that any document which is</FONT>
<BR><FONT SIZE=2>cited as a reference in a 3GPP specification is, in turn, a publicly</FONT>
<BR><FONT SIZE=2>available document).</FONT>
<BR><FONT SIZE=2> </FONT>
<BR><FONT SIZE=2>On Tom Taylor's point about the stability of the specifications, we agreed</FONT>
<BR><FONT SIZE=2>at last week's working group meeting that the specifications are now ready</FONT>
<BR><FONT SIZE=2>for approval (which means that they will be brought under a formal change</FONT>
<BR><FONT SIZE=2>control system). They will be presented for approval at the meeting of</FONT>
<BR><FONT SIZE=2>Technical Specification Group Core network next week (14 - 16 March) in Palm</FONT>
<BR><FONT SIZE=2>Springs, CA.</FONT>
<BR><FONT SIZE=2> </FONT>
<BR><FONT SIZE=2>I hope this helps.</FONT>
<BR><FONT SIZE=2> </FONT>
<BR><FONT SIZE=2>Best regards</FONT>
<BR><FONT SIZE=2> </FONT>
<BR><FONT SIZE=2>Ian Park</FONT>
<BR><FONT SIZE=2>___________________________________________________ </FONT>
<BR><FONT SIZE=2>Ian Park</FONT>
<BR><FONT SIZE=2>Chief Engineer, Core Network Signalling Standards</FONT>
<BR><FONT SIZE=2>Vodafone Limited</FONT>
<BR><FONT SIZE=2>*T: +44 1635 673 527 </FONT>
<BR><FONT SIZE=2>*F: +44 1635 233 562 </FONT>
<BR><FONT SIZE=2>?E: ian.park@vf.vodafone.co.uk </FONT>
<BR><FONT SIZE=2>___________________________________________________ </FONT>
<BR><FONT SIZE=2> </FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Tom-PT Taylor [<A HREF="mailto:taylor@nortelnetworks.com">mailto:taylor@nortelnetworks.com</A>]</FONT>
<BR><FONT SIZE=2>Sent: 26 February 2001 10:50</FONT>
<BR><FONT SIZE=2>To: IANA</FONT>
<BR><FONT SIZE=2>Cc: megaco@fore.com; itu-sg16@mailbag.intel.com; ian.park@vf.vodafone.co.uk</FONT>
<BR><FONT SIZE=2>Subject: RE: Quick question on a Request for package registration</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>3GPP is a public forum, and I believe their packages would be viewed as</FONT>
<BR><FONT SIZE=2>public. I'll note that it is desirable that the packages be considered</FONT>
<BR><FONT SIZE=2>technically stable (though perhaps subject to some editing and minor</FONT>
<BR><FONT SIZE=2>adjustment) before they are registered.</FONT>
</P>
<P><FONT SIZE=2>I've copied various parties for coordination purposes. </FONT>
</P>
<P><FONT SIZE=2>> -----Original Message----- </FONT>
<BR><FONT SIZE=2>> From: IANA [ <A HREF="mailto:iana@iana.org">mailto:iana@iana.org</A> <<A HREF="mailto:iana@iana.org">mailto:iana@iana.org</A>> ] </FONT>
<BR><FONT SIZE=2>> Sent: Friday, February 23, 2001 5:28 PM </FONT>
<BR><FONT SIZE=2>> To: Taylor, Tom-PT [NORSE:B881:EXCH] </FONT>
<BR><FONT SIZE=2>> Subject: FW: Quick question on a Request for package registration </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Tom, </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Quick question. Which range should these packages be registered in? </FONT>
<BR><FONT SIZE=2>> Do I need to ask the applicants if these are public or private? </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> From the RFC: </FONT>
<BR><FONT SIZE=2>> Public packages MUST be given serial numbers in the range 0x0001 to </FONT>
<BR><FONT SIZE=2>> 0x7fff. Private packages MUST be given serial numbers in the range </FONT>
<BR><FONT SIZE=2>> 0x8000 to 0xffff. </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Thanks for any help. If there is someone better to ask, please let me </FONT>
<BR><FONT SIZE=2>> know. Don't want to bug you :) </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Michelle </FONT>
<BR><FONT SIZE=2>> IANA </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> ************************************************************** </FONT>
<BR><FONT SIZE=2>> *********** </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Hi there </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I am the editor for a 3rd Generation Partnership Project </FONT>
<BR><FONT SIZE=2>> (3GPP) protocol </FONT>
<BR><FONT SIZE=2>> specification which defines extensions to the H.248/MeGaCo </FONT>
<BR><FONT SIZE=2>> protocol; I have </FONT>
<BR><FONT SIZE=2>> pasted in a copy of the "Scope" clause of this specification below. </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> "The present document describes the protocol to be used on </FONT>
<BR><FONT SIZE=2>> the Media Gateway </FONT>
<BR><FONT SIZE=2>> Controller (MGC) - Media Gateway (MGW) interface. The Media Gateway </FONT>
<BR><FONT SIZE=2>> Controllers covered in this specification are the MSC server </FONT>
<BR><FONT SIZE=2>> and the GMSC </FONT>
<BR><FONT SIZE=2>> server. The basis for this protocol is the H.248/MEGACO protocol as </FONT>
<BR><FONT SIZE=2>> specified in ITU-T and IETF. The BICC architecture as </FONT>
<BR><FONT SIZE=2>> described in ITU-T </FONT>
<BR><FONT SIZE=2>> Q.1902 [7]-[11] and 3G TS 23.205 [3] defines the usage of </FONT>
<BR><FONT SIZE=2>> this protocol. </FONT>
<BR><FONT SIZE=2>> This specification describes the changes to H.248/MEGACO </FONT>
<BR><FONT SIZE=2>> which are needed to </FONT>
<BR><FONT SIZE=2>> handle 3GPP specific traffic cases. This is done by using the </FONT>
<BR><FONT SIZE=2>> H.248/MEGCO </FONT>
<BR><FONT SIZE=2>> standard extension mechanism. </FONT>
<BR><FONT SIZE=2>> The present document is valid for a 3rd generation PLMN </FONT>
<BR><FONT SIZE=2>> (UMTS) complying </FONT>
<BR><FONT SIZE=2>> with Release 2000 and later. " </FONT>
<BR><FONT SIZE=2>> We need to define three new packages for this specification, </FONT>
<BR><FONT SIZE=2>> and as the </FONT>
<BR><FONT SIZE=2>> custodians of the package identifiers you are the people I </FONT>
<BR><FONT SIZE=2>> need to contact </FONT>
<BR><FONT SIZE=2>> to ask for the package numbers! </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I have pasted in the first part of the definition of each </FONT>
<BR><FONT SIZE=2>> package below. </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> 13.1.1 IuUP package. </FONT>
<BR><FONT SIZE=2>> PackageID: 3giuup (0x####) </FONT>
<BR><FONT SIZE=2>> [Editor's note: PackageID to be allocated by IANA] </FONT>
<BR><FONT SIZE=2>> Version: 1 </FONT>
<BR><FONT SIZE=2>> Extends: None </FONT>
<BR><FONT SIZE=2>> This package identifies that the Iu User Plane is used for </FONT>
<BR><FONT SIZE=2>> the termination. </FONT>
<BR><FONT SIZE=2>> It also contains some parameters for the Iu User Plane </FONT>
<BR><FONT SIZE=2>> functions in the MGW. </FONT>
<BR><FONT SIZE=2>> The Iu User Plane is active in both directions independently </FONT>
<BR><FONT SIZE=2>> of the Stream </FONT>
<BR><FONT SIZE=2>> Mode. </FONT>
<BR><FONT SIZE=2>> 13.1.2 Circuit Switched Data package </FONT>
<BR><FONT SIZE=2>> PackageID: 3gcsd (0x####) </FONT>
<BR><FONT SIZE=2>> [Editor's note: PackageID to be allocated by IANA] </FONT>
<BR><FONT SIZE=2>> Version: 1 </FONT>
<BR><FONT SIZE=2>> Extends: None </FONT>
<BR><FONT SIZE=2>> This package contains the information needed to be able to </FONT>
<BR><FONT SIZE=2>> support GSM and </FONT>
<BR><FONT SIZE=2>> UMTS Circuit Switched Data from the media gateway. </FONT>
<BR><FONT SIZE=2>> 13.1.3 TFO package </FONT>
<BR><FONT SIZE=2>> PackageID: 3gtfoc (0x####) </FONT>
<BR><FONT SIZE=2>> [Editor's note: PackageID to be allocated by IANA] </FONT>
<BR><FONT SIZE=2>> Version: 1 </FONT>
<BR><FONT SIZE=2>> Extends: None </FONT>
<BR><FONT SIZE=2>> This package defines events and properties for Tandem Free </FONT>
<BR><FONT SIZE=2>> Operation (TFO) </FONT>
<BR><FONT SIZE=2>> control. TFO uses inband signalling and procedures for </FONT>
<BR><FONT SIZE=2>> Transcoders to enable </FONT>
<BR><FONT SIZE=2>> compressed speech to be maintained between a tandem pair of </FONT>
<BR><FONT SIZE=2>> transcoders. </FONT>
<BR><FONT SIZE=2>> This package allows an MGW which has inserted a transcoder to </FONT>
<BR><FONT SIZE=2>> support TFO. </FONT>
<BR><FONT SIZE=2>> Can you please let me know how I should go on from here to </FONT>
<BR><FONT SIZE=2>> have the package </FONT>
<BR><FONT SIZE=2>> numbers allocated? If you need any further information, </FONT>
<BR><FONT SIZE=2>> please contact me. </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Best regards </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Ian Park </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> ___________________________________________________ </FONT>
<BR><FONT SIZE=2>> Ian Park </FONT>
<BR><FONT SIZE=2>> Chief Engineer, Core Network Signalling Standards </FONT>
<BR><FONT SIZE=2>> Vodafone Limited </FONT>
<BR><FONT SIZE=2>> *T: +44 1635 673 527 </FONT>
<BR><FONT SIZE=2>> *F: +44 1635 233 562 </FONT>
<BR><FONT SIZE=2>> *E: ian.park@vf.vodafone.co.uk </FONT>
<BR><FONT SIZE=2>> ___________________________________________________ </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
</BODY>
</HTML>