RE: Summary of work areas

["Christian Huitema" <huitema@windows.microsoft.com>]

My own list of task includes:

- description of an incremental roadmap that makes "business sense"
- solving the egress filtering issue (including when addresses cannot be
rewritten)
- selection of a first pair of address/locator to "establish contact",
either from application to TCP (as in the DT2 proposal or in the NOID
proposal) or from identifier to locator (in the SIM proposal)
- learning the set of addresses/locators associated to the
"distinguished address/locator" (common to DT2 proposal and NOID -- the
DNS is only one of many possibilities)
- decision algorithm for actually triggering the use of a different set
of addresses/locators for an ongoing TCP connection (we should consider
the trade-off between routing events, mobility events, and transport
events such as retransmit on timer)
- threat model & possible mitigations of the various attacks

-- Christian Huitema


> -----Original Message-----
> From: owner-multi6@ops.ietf.org [mailto:owner-multi6@ops.ietf.org] On
> Behalf Of Kurt Erik Lindqvist
> Sent: Wednesday, November 12, 2003 7:46 PM
> To: Tony Li
> Cc: multi6@ops.ietf.org
> Subject: Re: Summary of work areas
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> Oh, and I think the bootstrap/start-up face that Margaret and others
> brought up is something that should be on the list.
> 
> - - kurtis -
> 
> On onsdag, nov 12, 2003, at 21:02 Europe/Stockholm, Tony Li wrote:
> 
> >
> > Hi,
> >
> > To help Elliot out, I'd like for us to start thinking
> > about our top level work items.  As top level items,
> > they should, IMHO, be as independent as possible (tho
> > not wholly independent).  They should not be nested and
> > they should not be about the details.
> >
> > Here's a strawman:
> >
> >
> > Threat analysis
> > Locator storage & distribution
> > Mappings between locators, identifiers, and FQDNs
> > Security solutions
> > Exit addressing
> >
> > Additions, modifications?
> >
> > Tony
> >
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.0.2
> 
> iQA/AwUBP7L+YKarNKXTPFCVEQICiACdFjR3qVo8No4pMrzHdLqJhZ628TUAoLpV
> CMtZwn3Q2m8V3ibnTY+sIHdn
> =J+q6
> -----END PGP SIGNATURE-----
>