RE: More Comments on draft-ietf-mobike-design-01.txt
| Newsgroups | gmane.ietf.mobike |
|---|---|
| Message-ID | <DC504E9C3384054C8506D3E6BB01246002DF4D55@bsebe001.americas.nokia.com> |
> -----Original Message----- > From: [email protected] > [mailto:[email protected]]On > Behalf Of ext > Sent: Friday, January 14, 2005 4:45 PM > To: [email protected] > Subject: [Mobike] More Comments on draft-ietf-mobike-design-01.txt > > 4) 4. Framework > Although the interaction with other protocols to determine > the preferred > address and preferred address set is important for MOBIKE > to operate correctly the working group is chartered to > consider this > aspect out of scope. The working group will develop a MOBIKE > protocol with the following functionality: > o Ability to inform a peer about the peer address set > o Ability to inform a peer about the preferred address > o Ability to test connectivity along a path and thereby > to detect an > outage in order to fall back to another address, > thereby making it > the new preferred address > o Ability to change the peer address set > o Ability to deal with Network Address Translation devices How about the 4th bullet be: o Ability to change the peer address set and the preferred address For the Mobility scenario, the preferred address shall need to be changed. Or is it subsumed in the bullets 1 and 2? Atul