- sg16-avd - lists.packetizer.com

COM16-D332: GW Control aspects of G.IP2IP
by Albrecht.Schwarz＠alcatel.de 24 Mar '06

24 Mar '06

Hi Peter, just read your D332. Some comments in advance: The signalling requirements draft TR Q.ncap2 reminds me to H.248 Profiles. Guess ETSI's H.248 Profiles for IP-to-IP gateways (TS 102 333, successor ES 283 018) matching very close the majority of sketched signalling requirements. My assumption is, that the signalling interface ("in case there are signalled services on a call indidvidual level") of G.IP2IP is based on H.248. Just as G.799.1 is based on H.248. Now, H.248 Profiles for IP-to-IP gateways could be phased concering various criteria (like with or w/o QoS at IP interface, with or w/o edge router functions (like MPLS LER, or DiffServe ER), or with or w/o media awareness, or others). With regards to the "media support" aspect, the two main phases are: 1. media-agnostic H.248 Profiles for IP-to-IP gateways 2. media-aware H.248 Profiles for IP-to-IP gateways Presently, defined H.248 Profiles are available for (1), work on (2) is in progress (e.g., MSF). Practically phasing could be realized by a next Profile version, i.e., (2) extends the capabilites of (1). My conclusions: * might be worth to consider a similar G.IP2IP phasing, e.g., G.IP2IP.1 = media-agnostic, G.IP2IP.2 = additional media-awareness * general: could imagine that additional H.248 Profile specifications as separate documents to G.IP2IP or G.799.1 could be beneficial complementary information (incl. off-loading G.x-series GW specifications from H.248 details) Regards, Albrecht

1 0

COM16-D332: GW Control aspects of G.IP2IP
by Albrecht.Schwarz＠alcatel.de 24 Mar '06

24 Mar '06

Hi Peter, just read your D332. Some comments in advance: The signalling requirements draft TR Q.ncap2 reminds me to H.248 Profiles. Guess ETSI's H.248 Profiles for IP-to-IP gateways (TS 102 333, successor ES 283 018) matching very close the majority of sketched signalling requirements. My assumption is, that the signalling interface ("in case there are signalled services on a call indidvidual level") of G.IP2IP is based on H.248. Just as G.799.1 is based on H.248. Now, H.248 Profiles for IP-to-IP gateways could be phased concering various criteria (like with or w/o QoS at IP interface, with or w/o edge router functions (like MPLS LER, or DiffServe ER), or with or w/o media awareness, or others). With regards to the "media support" aspect, the two main phases are: 1. media-agnostic H.248 Profiles for IP-to-IP gateways 2. media-aware H.248 Profiles for IP-to-IP gateways Presently, defined H.248 Profiles are available for (1), work on (2) is in progress (e.g., MSF). Practically phasing could be realized by a next Profile version, i.e., (2) extends the capabilites of (1). My conclusions: * might be worth to consider a similar G.IP2IP phasing, e.g., G.IP2IP.1 = media-agnostic, G.IP2IP.2 = additional media-awareness * general: could imagine that additional H.248 Profile specifications as separate documents to G.IP2IP or G.799.1 could be beneficial complementary information (incl. off-loading G.x-series GW specifications from H.248 details) Regards, Albrecht

1 0

Contributions to the next month SG16 meeting
by OKUBO Sakae 22 Mar '06

22 Mar '06

Dear experts, The following four contributions have been voluntarily posted at the avc-site to facilitate your advance review: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0604_Gen/ ftp://ftp3.itu.int/avc-site/2005-2008/0604_Gen user: avguest password: Avguest 200604SG16_KDDI_2_NGNterminal.zip -- Q.24 KDDI: A notification scheme of the QoS information for NGN terminals H.FSIC_Update.zip -- Q.25 University of North Carolina: H.FSIC Update Work_Plan_for_Next_Generation_H.350_Services.zip -- Q.4 University of North Carolina: Work Plan for Next Generation H.350 Services Educational_Perspectives_on H.325_Requirements.zip -- Q.21 University of North Carolina: Educational Perspectives on H.325 Requirements -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ******************************************************************

1 0

Re: AW: Documents for the SG16 meeting (3-13 April)
by OKUBO Sakae 15 Mar '06

15 Mar '06

Dear Mr. Lehmann, At 14:29 +0100 06/03/13, <Leo.Lehmann(a)bakom.admin.ch> wrote: >I have sent the attached document already to TSB for registration. >But may I also use your offer and ask you to upload the document to >the avc-site? Thank you. I have placed your document at the following site: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0604_Gen/MM_Service_Mobility… -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ******************************************************************

1 0

Re: Fw: SG16: Q3 contributions
by Albrecht.Schwarz＠alcatel.de 13 Mar '06

13 Mar '06

fyi, 3 more in http://ties.itu.int/u/itu-t/edh/sg16/ Albrecht Alcatels1 T05-SG16-060403-D H.248.38 BC Editorial.doc 13-Mar-2006 15:24 51k Alcatelt1 T05-SG16-060403-D H.248.1 StatisticsDescriptorEd04.doc 13-Mar-2006 15:24 302k T05-SG16-060403-D H.248.SPDSPEC_Tables.zip 13-Mar-2006 15:25 56k Albrecht SCHWARZ To: tsbedh(a)ITU.INT 13.03.2006 15:02 cc: Albrecht SCHWARZ/DE/ALCATEL@ALCATEL Subject: Fw: SG16: Q3 contributions fyi, I've submitted some more (currently = 26 contributions from ALCATEL) Regards, Albrecht Schwarz http://ties.itu.int/u/itu-t/edh/sg16/ Alcatela1 T05-SG16-060403-D H.248.1 MID_PortRedirectionEd01.doc 11-Mar-2006 12:14 114k Alcatela4 T05-SG16-060403-D H.248.1 IMG Editorial § 6.3.doc 11-Mar-2006 12:14 88k Alcatela5 T05-SG16-060403-D H.248.1 IMG ErrorCode in § 6.3.2.doc 11-Mar-2006 12:14 91k Alcatela6 T05-SG16-060403-D H.248.1 IMG TestState.doc 11-Mar-2006 12:14 181k Alcatela7 T05-SG16-060403-D H.248.1 IMG ServiceChangeMgcID.doc 11-Mar-2006 12:14 92k Alcatelk1 T05-SG16-060403-D H.248.4 FurtherDiscussion 20060223.doc 11-Mar-2006 12:14 161k Alcatelk2 T05-SG16-060403-D H.248.4 ModifiedProposal 20060223.doc 11-Mar-2006 12:14 112k Alcatelm1 T05-SG16-060403-D H.Sup7.H248CtrlAssoc Ed03.doc 11-Mar-2006 12:15 258k Alcatelm2 T05-SG16-060403-D H.Sup7 Phases.doc 11-Mar-2006 12:15 98k Alcatelm3 T05-SG16-060403-D H.Sup7 AddressChanges.doc 11-Mar-2006 12:15 94k Alcatelm4 T05-SG16-060403-D H.Sup7 MIDoperations.doc 11-Mar-2006 12:15 91k Alcatelm5 T05-SG16-060403-D H.Sup7 SCTPassociationEstablishment.doc 11-Mar-2006 12:15 105k Alcatelp1 T05-SG16-060403-D H.248.44 MLPPcomments.doc 13-Mar-2006 14:57 75k Alcatelp2 T05-SG16-060403-D H.248.44 Definitions.doc 13-Mar-2006 14:57 85k Alcatelp3 T05-SG16-060403-D H.248.44 InterworkingH.323.doc 13-Mar-2006 14:57 222k Alcatelp4 T05-SG16-060403-D H.248.44 eMLPP.doc 13-Mar-2006 14:57 86k Alcatelr1 T05-SG16-060403-D H.248.gm_gc_Package_Ed01_20051220.doc 11-Mar-2006 12:15 107k Alcatelr2 T05-SG16-060403-D H.248.gm_gc_Package_Ed02_Adaptations.doc 11-Mar-2006 12:15 116k Alcatelr3 T05-SG16-060403-D H.248.gm_gc_Package_ValueRange.doc 11-Mar-2006 12:15 88k Alcatelv1 T05-SG16-060403-D H.248.GC PolicyEnforcement_Filtering.doc 11-Mar-2006 12:15 116k Alcatelw1 T05-SG16-060403-D H.248.43 RTPXtalk Ed03.doc 13-Mar-2006 11:48 227k Alcatelw2 T05-SG16-060403-D H.248.43 RTPXtalk SymmetricRTP.doc 13-Mar-2006 11:48 119k Alcately1 T05-SG16-060403-D H.248.40 Editorial.doc 11-Mar-2006 12:15 97k Alcately2 T05-SG16-060403-D H.248.40 OutgoingDirection.doc 11-Mar-2006 12:15 85k Alcately3 T05-SG16-060403-D H.248.40 AppI VoRTP.doc 11-Mar-2006 12:15 101k Alcately4 T05-SG16-060403-D H.248.40 AppII Pa2PaDeadlockLatching.doc 11-Mar-2006 12:15 105k ----- Forwarded by Albrecht SCHWARZ/DE/ALCATEL on 13.03.2006 15:00 ----- Albrecht SCHWARZ/DE/ALCAT To: tsbedh(a)ITU.INT EL@ALCATEL cc: itu-sg16(a)external.cisco.com Subject: SG16: Q3 contributions 11.03.2006 12:31 fyi, I've dropped a first set of H.248 related contributions in the ftp box for SG16: /u/itu-t/edh/sg16 Albrecht

1 0

SG16: Q3 contributions
by Albrecht.Schwarz＠alcatel.de 11 Mar '06

11 Mar '06

fyi, I've dropped a first set of H.248 related contributions in the ftp box for SG16: /u/itu-t/edh/sg16 Albrecht

1 0

Documents for the SG16 meeting (3-13 April)
by OKUBO Sakae 09 Mar '06

09 Mar '06

Dear WP2/16 experts, Since this meeting is of Study Group level, all the documents are handled by TSB, not by a Rapporteur. However, you may wish to upload your documents to the avc-site on a volunteering basis for advance review by the experts. In that case, place your document at: ftp://ftp3.itu.int/avc-site/Incoming/ user: avguest password: Avguest or email it to me, then I will move it to: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0604_Gen/ ftp://ftp3.itu.int/avc-site/2005-2008/0604_Gen user: avguest password: Avguest -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ******************************************************************

1 0

RE: April Meeting Accomodation
by Paul E. Jones 09 Mar '06

09 Mar '06

Christian, I tried booking a room when I was there last November and couldn't for the same reason. I was hopeful that some space would open, but I've not yet tried to book my room, either. This is most unfortunate. So, I'll take any advise you receive. Paul > -----Original Message----- > From: Christian Groves [mailto:cngroves@bigpond.net.au] > Sent: Wednesday, March 08, 2006 7:44 AM > To: SG16 > Subject: April Meeting Accomodation > > Hello, > > Sorry to use the exploder for this... > > Unfortunately it seems Hotel availability for the April SG16 meeting is > at a premium between the 3rd and the 7th and I've left it a bit too > late. If anyone was in the same boat and has found a solution and or > could recommend a hotel with availability i'd appreciate if you could > send me an email. > > Thanks. > > Regards, Christian >

1 0

April Meeting Accomodation
by Christian Groves 08 Mar '06

08 Mar '06

Hello, Sorry to use the exploder for this... Unfortunately it seems Hotel availability for the April SG16 meeting is at a premium between the 3rd and the 7th and I've left it a bit too late. If anyone was in the same boat and has found a solution and or could recommend a hotel with availability i'd appreciate if you could send me an email. Thanks. Regards, Christian

1 0

progress of draft H.460.mb "Message Broadcast for H.323 Systems" and related security issues: call for contributions
by Euchner, Martin 02 Mar '06

02 Mar '06

Dear all, Q.2/16 has scheduled Draft ITU-T Recommendation H.460.mb "Message Broadcast for H.323 Systems" for possible consent at the forthcoming SG16 meeting in April. The latest draft of H.460.mb is available at: http://ftp3.itu.ch/av-arch/avc-site/2005-2008/0511_Gen/AVD-2813a.zip Unfortunately, Q.25 did not have discussion of the potential security issues around H.460.mb at the last joint Rapporteurs Meeting in November 2005/Geneva. The draft text raises a few security questions as open issues within Editor notes; there may or may not be more security issues which are not yet identified in the text; and there are also other non-security issues in the document that may deserve some closer view. Together with Paul Jones (Q.2/16 Rapporteur), I would like to take this opportunity to raise the issue at this point in time with the intention to solicit mailing list discussion and/or call for input contributions into the next SG16 meeting, allowing the two Questions to have a fruitful discussion on the draft and to determine how we move forward. Allow me to make a couple of remarks and also ask a few guiding questions: - H.460.mb operates in a multicast environment where H.323-based announcement servers broadcast to a pre-defined set of H.323 receivers/endpoints. As such, we could be interested to study how to secure such an environment. What type of security do we need, how to secure the involved entities? - To which degree can we leverage existing H.235.x Recommendations for usage in H.460.mb? - Where (signaling protection, media protection) do we need to study new (multicast) security mechanisms for this particular application? - Can we re-use any existing work from other groups for this purpose? - Should security for H.460.mb be addressed at this point in time, or can we add-in whatever security measures are necessary at a later/future point in time? - If we have to do something at least on security, what should it be about? What is the most pressing requirement from the market point of view? - Which security infrastructure is adequate for such a multicast scenario? Shared keys, PKI; key management, statically configured, dynamic negotiable? - ... Looking forward to your interest, feedback, views, contributions... With kind regards Martin Euchner. --------------------------------------------------------------------- | Dipl.-Inf. Rapporteur Q.25/16 | Martin Euchner Phone: +49 89 722 55790 | Siemens AG.....................Fax : +49 89 722 62366 | COM GCM PS 3 mailto:Martin.Euchner@siemens.com | mailto:martin.euchner@ties.itu.int | Hofmannstr. 51 Intranet: http://ietf.icn.siemens.de/sr3/Standardisation_Topics/security/ | D-81359 Muenchen Internet: http://www.siemens.de/ | __________________ | Germany ---------------------------------------------------------------------

1 0