Re: Reminder re multi6 drafts

[Brian E Carpenter <brc@zurich.ibm.com>]

Jim,

We understand of course that there are only 168 hours a week.

The WG will have to take an architectural decision at some point
whether to pursue transport layer solution(s). Without the SCTP
case being on the table, we will be handicapped. If anybody else
feels like doing even a superficial job on SCTP in the next few
days, that would be very helpful.

   Brian

"Bound, Jim" wrote:
> 
> SCTP will not happen before this month.  Randy, Yanick, and I cannot get
> it done.  Sorry.
> /jim
> 
> > -----Original Message-----
> > From: owner-multi6@ops.ietf.org
> > [mailto:owner-multi6@ops.ietf.org] On Behalf Of Brian E Carpenter
> > Sent: Tuesday, January 20, 2004 1:36 PM
> > To: multi6@ops.ietf.org
> > Subject: Re: Reminder re multi6 drafts
> >
> >
> > It's getting very close to the end of January. We are still
> > hoping for HIP and SCTP based drafts this month, so that they can
> > be thoroughly analyzed before the IETF.
> >
> >    Brian
> >
> > Brian E Carpenter wrote:
> > >
> > > Folks,
> > >
> > > Just a reminder that we'd like all updated or new drafts describing
> > > possible approaches to solutions for multi6 to be submitted in the
> > > near future. We originally suggested a hard deadline of the end
> > > of December, but since people found that too rigid, let's try for
> > > having all the I-Ds available by mid-January at the latest.
> > > In addition to the existing proposals discussed in Minneapolis,
> > > we are at least expecting HIP and SCTP based contributions.
> > >
> > > We do ask that each draft includes a *short*
> > self-assessment against the
> > > goals in RFC 3582. For convenience, please name them as
> > >   draft-AUTHOR-multi6-...
> > >
> > > Please remember that one of our objectives is to identify
> > architectural
> > > components that occur in the various proposals.
> > >
> > > The co-chairs are acutely aware that the published charter for this
> > > WG is out of date. We do plan to fix that.
> > >
> > >    Brian
> > >    multi6 co-chair
> > > --