At Thu, 11 Jul 2002 10:59:27 +0200, Brian E Carpenter wrote:
>
> All of which tells me that if we define a requirement for the flow label
> allocation process to survive reboots, it will be a SHOULD not a MUST.
> A toaster would provide a compelling argument for overriding the SHOULD.
Precisely
2553bis (Basic API) status and plan:
As mentioned in Margaret's recent mail about the IPv6 WG Priority List:
>Basic Sockets Extensions
>Status: In IESG for Informational, update may be
> required to resolve normative reference
The current Basic
It has been over an hour, and this hasn't shown up on the list yet, so
I thought I would try it again...
Margaret
>Date: Fri, 12 Jul 2002 03:24:58 -0400
>To: [EMAIL PROTECTED]
>From: Margaret Wasserman <[EMAIL PROTECTED]>
>Subject: Fwd: Draft Agenda for Yokohama IETF IPv6 W.G. Sessions
>
>
>H
Hi All,
Here is an updated IPv6 agenda, reflecting the comments that we
have received this week.
I look forward to seeing you all in Yokohama!
Margaret
Internet Protocol version 6 WG (ipv6)
Thursday, July 18th, 0900-1130 & 1300-1500 (Room 301/302)
==
