Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt

See below.
>
> On 10/10/2016 3:15 AM, Gorry (erg) wrote:
>> ... There is no document in the RFC series that document UDP API - this
>> may be helpful roadmap to find this info. Two documents are easier to
>> maintain and cite than one.
>
> RFC1122 defines one in Section 4.1.4, but it basically points off to a
> definition of the IP API in Section 3.4, which ignores the issue of
> controlling source and destination ports.
>
> The true UDP API ought to be defined in the same way the TCP API is
> defined in RFC793, FWIW.
>
OK, so in the context of TAPS, the WG called for a list of UDP services.
This is what is in the  ID. I thought there may something useful to
publishing this as a companion INFO RFC alongside the connection-oriented
services ID. I suggest it may help to indicate what an App may need to
know to use UDP.

This ID clearly isn't an API spec.

> I've proposed a way forward for UDP options; as a result, I'd be glad to
> take a shot at a draft UDP API doc if useful.

I don't personally know whether an API spec for UDP is useful or not, but
suspect the list of services needed by UDP Apps is the thing the WG is
presnetly looking for.

Gorry

> Joe
>
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps
>