Subject: [RAI] Minutes of 3GPP - IETF telco on 21st October 2009

From: <[email-masked]>
Date: Sun, 25 Oct 2009 18:22:31 +0100

Dear all,

let me share with you the minutes of the latest 3GPP - IETF telco:

Date: 21st Oct 2009
Time: 15:00 - 17:00 UTC
Venue: Phone conference
Participants:
Hannu Hietalahti (notetaker)
Atle Monrad
Hannes Tschofenig
Georg Mayer
Peter Schmitt
Milan Patel
Keith Drage
Gonzalo Camarillo
Ben Campbell
Robert Sparks
Adam Roach
Ralph Droms
Jari Arkko
Jonne Soininen

Agenda:
-------------
1. Roll call
2. Review of action points
3. IP mobility (shift later in the agenda)
4. Joint workshops in November 2009 and March 2010 (shift later in the agenda)
5. IANA registrations
        - 3gpp-ims+xml MIME type
        - Diameter command codes
6. Emergency calls
7.Review of 3GPP IETF dependency document
8. Next meeting
9. AOB
10. Closing

1.      Roll call
All participants introduced themselves.

2.      REview of action points
AP      Title   Responsible     Status
1       Request expert comments on the best approach to IANA registration of Service ID namespace assignment    Mary Barnes     Closed
2       Check the registration status of IANA registration of 3gpp-ims+xml      Cullen Jennings Closed
3       Provide a written explanation of why it could be considered that IANA registration of feature tags g.3gpp.icsi and g.3gpp.iari could proceed according to RFC 2506 without procedural change    Atle Monrad     Closed
4       Escalate the previous summary by Atle for RAI leadership review during IETF #74 to find a recommended way forward       Cullen Jennings Closed
5       Report the SA3 meeting outcome to Jari Arkko    Valtteri Niemi  Closed
6       Arrange a telco on media security on Friday the 7th of Nov 2008 Valtteri Niemi  Closed
7       Find the original 3gpp-ims+xml registration document and forward it to Cullen   Hannu Hietalahti        Closed
8       Set up a meeting between 3GPP and IETF to agree how to proceed in the IANA registration of feature tags g.3gpp.icsi and g.3gpp.iari     Gonzalo Camarillo       Closed
9       Check the real 3GPP need for draft-arkko-mext-rfc3775-altcoa-check      Raj Patil       Closed
10      Hannu to ask on CT1 mailing list if anyone knows any reason why phonebcp -draft would not be applicable in cellular environment Hannu   Closed
        New APs assigned in this meeting
11
12
13

3.      IP mobility items
IPv4 support for PMIP6 in draft-ietf-netlmm-pmip6-ipv4-support is one of the critical Rel-8 dependencies. The draft has been in IESG evaluation since September 2009. Most other technical comments have been solved already, but the use of IPSec together with DSMIP is still under technical discussion.

It was foreseen that the draft could still progress by the end of the year.

The outcome of NETLMM mobility extensions BOF which was held a while ago has been subject to debate that has not converged to a single solution.

4.      Joint workshops in November 2009 and March 2010
Two IPv6 migration workshops have been discussed recently in 3GPP. The first one in November in Shanghai right before IETF #76 is informal meeting of colleagues interested in IPv6 and it is not shown in 3GPP meeting calendar as 3GPP event. IETF shares this view.

The second one in San Francisco in March 2010 is shown on 3GPP meeting calendar as an informal workshop which means that it cannot make changes on 3GPP specifications. Any output from the workshops needs to be consolidated via normal 3GPP contribution procedures. The main goal is to share the understanding of requirements and solutions on IPv6 migration. The related 3GPP working groups are SA2, CT1, CT3 and CT4. Both workshops will be hosted by China Mobile.

Liaison Statement on the March 2010 workshop was sent to IETF in SP-090671 has been sent to IETF and Ralph Droms has already volunteered to facilitate a reply to determine the status of the meeting from IETF side in IESG.

In general there is interest on IETF side on IPv6 migration and a reply to the 3GPP LS in SP-090671 is being processed in IETF with the intention to reply in writing. The affected 3GPP working groups start their next meeting round on the 9th of November 2009 which makes a target for sending the reply.

5.      IANA registrations
5.1     IANA registration of 3gpp-ims+xml
IANA registration of the MIME type for 3gpp-ims+xml has eventually been completed. This required one further change of 3GPP definition of the MIME type in 3GPP TS 24.229. The CR was approved in TSG CT #45 in September 2009 and the IANA registration is based on the resulting new reference version 8.9.0.

5.2     IANA registration of new command codes
Enhancements to 3GPP network interfaces running Diameter often require new Diameter command codes to be defined. Up to now it has not been possible to IANA register new command codes without an IETF draft and this has led to production of formal IETF documents that fulfill the procedural requirements by referencing to already defined new command codes outside IETF.

draft-dime-diameter-cmd-iana defines a new process for IANA registration of new command codes. The main difference is the possibility to register command codes with direct reference to non-IETF document, such as 3GPP TS. This will help the work on 3GPP side by removing the need for dummy IETF drafts that would anyway point to the 3GPP TS. The draft is already approved by IESG.

6.      Emergency calls
Draft-patel-ecrit-sos-parameter is in publication requested phase but some further technical comments were made on the latest version by Cullen Jennings and thus a new version will be required.

A part of emergency callback work has been held back in 3GPP due to lack of progress in the related IETF work. Specific processing requirements set for PSAP callback to the user require some suitable marking of the callback from PSAP to the user. PSAP callback is now part of 3GPP Rel-9 requirements, so this would need to be addressed urgently as Rel-9 is expected to freeze in December 2009.

It should be checked whether the solution requires IETF work or not, but this could not be determined  during the meeting. Hannes to outline the currently available candidate mechanisms and Hannu to distribute them for SA2 review.

7.      Review of 3GPP - IETF dependency document
The following new Rel-8 dependencies have been identified since the previous update of the dependency document:
*       daft-ietf-ipsecme-ikev2-redirect
*       daft-ietf-dime-diameter-cmd-iana

Both new dependencies are already approved by IESG and in RFC editor's queue.

The applicability of phonebcp-draft has been discussed in the past. Based on Hannu's email request the 3GPP WGs have reviewed it and SA2 has also provided their comments in an LS.

CT1 have agreed to replace their references to draft-ietf-sipping-config-framework with references to draft-ietf-sip-xcapevent in 3GPP TS 24.141, 24.229, 24.523 and 24.623. These are believed to be the only 3GPP specifications referencing to the config-framework draft, so 3GPP does not need that draft any more.

CT3 have already replaced their reference to mahy-iptel-cpc with new reference to draft-patel-dispatch-cpc-oli-parameter. CT1 dependency to mahy-iptel-cpc still exists.

Draft-yu-tel-dai is indicated as dead in the I-D tracker, but the intention is to submit a new version to DISPATCH group.

The status of ietf-mip4-rfc3344bis says "waiting for writeup", i.e. it could be ready to be sent to the IESG. To be checked whether this can move forward or is there some issue that still needs to be dealt with?

muhanna-mext-binding-revocation should be draft-ietf-mext-binding-revocation. SA2 and CT4 have already updated their references in 3GPP TS 23.402 and 29.275, so only the dependency document was out of date. The draft is in last stages of IESG review,
one issue remaining with the WG, and it should be possible to solve this hopefully
before next week.

das-mipshop-andsf-dhcp-options is in WGLC, not received by the ADs yet.
There was only one review comment.

mext-rfc3775bis is getting ready to be sent to the IESG.

8.      Next meeting
It was agreed to meet next time during IETF #76 in Hiroshima. The usual lunch meeting time slot on Tuesday cannot be used this time, so lunch break on Monday of the IETF #76 meeting week was tentatively selected as the next meeting time.

9.      Any Other business
It was agreed to collect comments and revisions on these minutes until Friday the 23rd of October so that Hannu can distribute the reviewed and agreed version on 3GPP TSG CT mailing list and IETF RAI and Internet mailing list by Monday the 26th of October.

10.     Closing
The meeting was closed at 16:05 UTC.

BR,
Hannu Hietalahti
3GPP TSG CT Chairman
tel: +358 40 5021724