Yes, I think this topic is very relevant to the work that can be done in updated transport APIs, specifically around Path Selection. This is relevant both for initial connection establishment (when we’re racing various transport protocols across different paths, we need to know which local addresses to use), and maintenance of connections that support migration or multipath (which addresses can they use for new flows). The address selection can also be inferred from other properties of the transport connection, such as how long-lived the connection needs to be.
Fernando, what’s your plan for your draft? It seems like a great reference for our drafts, and something we need to consider in our list of application preferences when creating transport connections. Thanks, Tommy > On Feb 13, 2018, at 1:15 PM, Aaron Falk <aaron.f...@gmail.com> wrote: > > Are there folks in TAPS who want to discuss IPv6 address selection? Fernando > has a draft on the topic and is wondering if TAPS would be a good home. > > --aaron > > ---------- Forwarded message --------- > From: Spencer Dawkins at IETF <spencerdawkins.i...@gmail.com > <mailto:spencerdawkins.i...@gmail.com>> > Date: Mon, Nov 27, 2017 at 8:50 AM > Subject: Fwd: IPv6 address usage problem statement? > To: <taps-cha...@ietf.org <mailto:taps-cha...@ietf.org>> > Cc: Fernando Gont <fg...@si6networks.com <mailto:fg...@si6networks.com>> > > > Dear TAPsters, > > Fernando Gont is working on a draft with recommendations about address > selection, and 6MAN thought he should also be talking to people in TSV. I > offered to connect him with you folks, because it seems like this is part of > the transport selection problem that TAPS was chartered to work on, so > perhaps relevant to your work. > > Could you let Fernando know how you'd like for him to proceed? > > Thanks! > > Spencer > > ---------- Forwarded message ---------- > From: Fernando Gont <fg...@si6networks.com <mailto:fg...@si6networks.com>> > Date: Wed, Nov 22, 2017 at 6:24 PM > Subject: Re: IPv6 address usage problem statement? > To: Spencer Dawkins at IETF <spencerdawkins.i...@gmail.com > <mailto:spencerdawkins.i...@gmail.com>> > Cc: "tsv-...@tools.ietf.org <mailto:tsv-...@tools.ietf.org>" > <tsv-...@tools.ietf.org <mailto:tsv-...@tools.ietf.org>> > > > > Hello, Spencer, > > Thanks so much for your prompt response! Please find my comments in-line... > > > On 11/22/2017 06:38 AM, Spencer Dawkins at IETF wrote: > > Hi, Fernando, > > > > On Sat, Nov 18, 2017 at 9:17 PM, Fernando Gont <fg...@si6networks.com > > <mailto:fg...@si6networks.com> > > <mailto:fg...@si6networks.com <mailto:fg...@si6networks.com>>> wrote: > > > > Folks, > > > > I presented our document draft-gont-6man-address-usage-recommendations > > at the 6man meeting during the IETF week in Singapore. During my > > presentation, it was mentioned that the Transport area might be > > interested in this work, too/alternatively. -- IIRC, somebody mentioned > > the TAPS wg, specifically. > > > > > > It's up to the working groups, of course, but TAPS is certainly a > > reasonable suggestion. > > > > TAPS was originally chartered to pay little or no attention to security, > > just to limit the scope of what was being investigated, but they've made > > enough progress that we're discussing an updated charter that will more > > clearly emphasize that investigating the security properties of > > transport protocols - which, if you write an application to the TAPS > > API, the API implementation would be making its own decisions about path > > selection as part of selecting transport protocols. > > > > IIUC, of course. > > > > Want me to contact the chairs, or let you? > > I guess if you would that would be better. > > Thanks so much! > > Best regards, > -- > Fernando Gont > SI6 Networks > e-mail: fg...@si6networks.com <mailto:fg...@si6networks.com> > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492 > > > > > > -- > --aaron > > =====Short message from my phone===== > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps
_______________________________________________ Taps mailing list Taps@ietf.org https://www.ietf.org/mailman/listinfo/taps
