MIPv6 bootstrapping in split scenario - PowerPoint PPT Presentation

About This Presentation
Title:

MIPv6 bootstrapping in split scenario

Description:

the FAILED_CP_REQUIRED attribute does not have any information about what is wrong ... This would require establishing trust between each MN and the DNS server. ... – PowerPoint PPT presentation

Number of Views:55
Avg rating:3.0/5.0
Slides: 8
Provided by: gerardog
Learn more at: https://www.ietf.org
Category:

less

Transcript and Presenter's Notes

Title: MIPv6 bootstrapping in split scenario


1
Dallas, March 2006
IETF 65th mip6 WG
Mobile IPv6 bootstrapping
in split scenario (draft-ietf-mip6-bootstrapping
-split-02)
Gerardo Giaretta James Kempf Vijay Devarapalli
2
Status Update
  • WGLC last December
  • New I-D available after WGLC
  • editorial issues solved
  • consensus on Proxy DAD on HoA the HA checks the
    uniqueness of the HoA, but the draft does not
    require it to perform DAD
  • issue on USE_ASSIGNED_HoA attribute solved
    (rejected)
  • There are still two technical open issues

3
Issue USE_ASSIGNED_HoA attribute
  • The draft specifies a new IKEv2 Notify Nessage
    Type (USE_ASSIGNED_HOA) in case the MN tries to
    perform HoA auto-configuration but it is not
    allowed
  • Proposal during WGLC
  • the HA may raise a FAILED_CP_REQUIRED instead
    using USE_ASSIGNED_HoA
  • Issue rejected and closed
  • the FAILED_CP_REQUIRED attribute does not have
    any information about what is wrong

4
Open issue DNS Update
  • Current solution specified in the WG draft
  • MN includes a new mobility option, the DNS Update
    option
  • HA performs DNS update on behalf of the MN using
    the HoA previously allocated and the FQDN
    provided by the MN in the DNS Update option
  • DNS Update mobility option
  • R flag used to request the removal of DNS entry
  • separate Status namespace for DNS update

5
Open issue DNS Update (contd)
  • Some concerns raised during WGLC
  • standard rule is to update only where you are
    trusted so the MN should update the direct DNS
    and the HA the reverse DNS
  • This would require establishing trust between
    each MN and the DNS server. HA updating the DNS
    entry is easier
  • the update should be a consequence of the
    allocation of the address, not of the home
    registration and thus the reverse update should
    be performed by the IKEv2 code
  • This would disallow a MN from specifiying which
    home address it wants to appear in the DNS server
  • No consensus to make the changes
  • Sticking to the current solution in the draft
  • DNS expert review requested

6
Open issue MIP6_HOME_PREFIX attr.
  • The draft specifies the MIP6_HOME_PREFIX
    configuration attribute in order to send Home
    Prefix to the MN
  • used for HoA auto-configuration
  • the WG draft currently proposes that only one
    prefix is advertised
  • proposals to have a broader CFG option, having
    the HA sending to the MN several prefixes
  • we still have MPD for that
  • IKEv2 CFG shouldnt be a replacement for a router
    advertisement
  • No consensus
  • IKEv2/IPsec expert review requested

7
Next Steps
  • Authors have requested that the WG chairs arrange
    for expert review on the draft prior to
    submission to the IESG
  • DNS expert review for DNS update issue
  • IKEv2 expert review for MIP6_HOME_PREFIX
    attribute issue
  • If these reviews will imply significant changes
    to the draft there will be another WGLC
Write a Comment
User Comments (0)
About PowerShow.com