Re: [mif] Fwd: New Version Notification for draft-kline-mif-mpvd-api-reqs-00.txt

[Stjepan Groš <[e-mail]>]

Hi Erik,

Thank you for the draft.

I have few comments/questions.

First, what I'm reading from the draft is that each PvD aware
application should have access to a single PvD at any single moment? If
that is so, what about mpTCP and SCTP applications that are PvD aware?
They should have access to multiple PvDs simultaneously for a fail over
reasons. So, how this draft takes into account that use case?

In section 3.4 there is a note/question about "loopback PvD". What we
were thinking/discussing is that there should be such a PvD for
backwards compatibility, i.e. for non-PvD aware applications that for
some reason expect all available connections and interfaces (PvDs) to be
present (non-PvD aware mpTCP and SCTP applications, UDP applications,
debugging applications like tcpdump/wireshark). This configuration we
called internally "root network name space".

SG

On 01.11.2015 16:08, Erik Kline wrote:
> All,
>
> Quite, quite late, but I took a stab at scrapping the presentation
> from Prague and writing instead an MPvD API requirements document.
>
> -ek
>
>
> ---------- Forwarded message ----------
> From: <[e-mail] <mailto:[e-mail]>>
> Date: 2 November 2015 at 00:03
> Subject: New Version Notification for draft-kline-mif-mpvd-api-reqs-00.txt
>
>
>
> A new version of I-D, draft-kline-mif-mpvd-api-reqs-00.txt
> has been successfully submitted by Erik Kline and posted to the
> IETF repository.
>
> Name:           draft-kline-mif-mpvd-api-reqs
> Revision:       00
> Title:          Multiple Provisioning Domains API Requirements
> Document date:  2015-11-01
> Group:          Individual Submission
> Pages:          15
> URL:           
> https://www.ietf.org/internet-drafts/draft-kline-mif-mpvd-api-reqs-00.txt
> Status:       
>  https://datatracker.ietf.org/doc/draft-kline-mif-mpvd-api-reqs/
> Htmlized:     
>  https://tools.ietf.org/html/draft-kline-mif-mpvd-api-reqs-00
>
>
> Abstract:
>    RFC 7556 [RFC7556] provides the essential conceptual guidance an API
>    designer would need to support use of PvDs.  This document aims to
>    capture the requirements for an API that can be used by applications
>    that would be considered "advanced", according to section 6.3 [1] of
>    RFC 7556 [RFC7556].  The "basic" [2] and "intermediate" [3] API
>    support levels can in principle be implemented by means of layers
>    wrapping the advanced API.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org
> <http://tools.ietf.org>.
>
> The IETF Secretariat
>
>