MIP4 WG - Thursday, March 13 13:00-15:00
         Scribe: Acee Lindem (acee@redback.com)

Document Status - Henrik Levkowetz

    - draft-ietf-mip4-generic-notification-message will goto last call
    - Review of documents requested:
             draft-ietf-mip4-nemo4-fa
             draft-ietf-mip4-nemo4-dynamic
             draft-ietf-mip4-udptunnel-mib
    - IESG Processing Several Documents

 Jari Arkko: Stated that prehaps draft-ietf-mip4-vpn-problem-statement should
             be changed from BCP to Standards Track now that it defines
             protocol behavior. 

 Henrik: Will re-last call - WG or IETF?

 Jari:    IETF Last call is fine. WG members can comment if they have an 
          issues with the change of status. 


 Home Agent Assisted Route Optimization  - Antti Makela (See Slides) 

      - Scalability Improvements 
         * Compression of IP prefixes and realms

 Charlie Perkins: MANET WG has been working prefix compression solution with
                  their Packet Building Block work. 

        http://www.ietf.org/internet-drafts/draft-ietf-manet-packetbb-12.txt

      - Return Routability 
         * Optional feature now. 

 Henrik: Should this be a candidate for MIP4 Re-charter? 
      4 in favor - 0 Against - Others ambivalent

  Diameter MIPv4 Application for Key Distribution - Ahmad Muhanna (See Slides)
      - Tutorial on 3GPP2 and WiMAX authentication in relation to Diameter
      - Specified Requirements for revised MIP4 Diameter 
        Application 
      - Hopes for consolidated WiMAX and 3GPP2 Diameter application

 Pete McCann: Do SDOs allow for dynamic HA assignment?
 Ahmad: Yes
 Pete: Is there a security exposure exposing the key to another HA?
 Avi Lior: It is based on AAA trust with all the HAs involved.
 Henrik: Where is this headed?
 Ahmad: Either revise RFC 4004 or another parallel application leaving 
        RFC 4044 as it is. The important thing is to decouple the signalling. 
 Henrik: So, you want this WG to provide input on whether this should
          be a WG item in DIME. 
 Ahmad: Pete and I discussed this and MIP4 must agree that this is the
        right thing to do. Requests blessing.
 Henrik: Requests comments.
 Pete: Be careful with distribution of SPIs.
 Ahmad: There is a single SPI to NAI mapping. 
 Henrik: Asymmetric SPIs are disallowed? 
 Ahmad: Not disallowed - SDO use symmetric SPIs.
 Pete: Same of different SPIs. Good to update application to get crypto 
       agility and other benefits. However, it may be difficult to completely
       decouple MIP4 and AAA signalling. 
 Avi: Keys derived EMSK will have crypto agility.
 Pete: Wants crypto agility for message digest as well. 
 Henrik: In the end, we want sufficient protection for our signalling. We
          need to pick it independent of the derivation of keys.
 Avi: WiMAX took seriously notion of identify hiding. 
      However, MIP4 uses an NAI. WiMAX used concept of psuedo-NAI. 
 Henrik: Are people interested in this?
 Acee: Will SDOs update their existing solutions? 
 Ahmad: Nobody has moved to DIAMETER (i.e., RFC 4004) yet. 
 Avi: WiMAX did not want to touch RFC 4004.
 George Tsirtsis: AAA is overloaded already. AAA is a bottleneck so
          administrators are reluctant to move further. 
 Sri Gundavelli: Supports Investigation
 Henrik: Believes there is a reasonable legitimete need for this work. 
          Should MIP4 WG work on a document pointing the way forward. 
 Ahmad: Replace RFC 4004 or new independent document. 
 Henrik: Not ready to commit to one or the other yet (although he has an 
          opinion). Wants a document.
 Sri: Also thinks we should have a document. 
 Pete: Agrees document would be best. 

  
Mobility Management using PMIP4/AAA Mobility Extensions - Vamsi Krishna 
 Gondi(See slides)
       - Architecture for PMIP4 and home/visited network AAA authentication
 Ahmad: Why is RRQ/RRP needed when you already had an initial exchange
        of authentication request/response?
 Vamsi: Different domains - can't be combined. 
 Ahmad: All the parties know what needs to be done. 
 Avi: WiMAX and 3GPP2 have solved this problem. Suggests different flow. 
 Vamsi: Will address other issues. 
 Pete: RADIUS application for MIP4 is on the charter. PMIP4 RADIUS is not
       on charter. We could do one for both MIP4 and PMIP4. 
 Avi: Would like to see one combined MIP4/PMIP4 RADIUS application. 
 Sri: PMIP4 is on informational track - how do we combine with
      standards track?
 Henrik: Should take as input to RADIUS. 
   
 Henrik: If no more, we're adjorned.