Re: Comments on draft-katz-yeung-traffic-08.txt

Don Goodspeed <dgoodspe@EXCITE.COM> Wed, 23 October 2002 18:51 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29666 for <ospf-archive@LISTS.IETF.ORG>; Wed, 23 Oct 2002 14:51:14 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <13.0078B1E3@cherry.ease.lsoft.com>; Wed, 23 Oct 2002 14:53:30 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 332558 for OSPF@DISCUSS.MICROSOFT.COM; Wed, 23 Oct 2002 14:53:28 -0400
Received: from 207.159.120.58 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Wed, 23 Oct 2002 14:53:28 -0400
Received: by xmxpita.excite.com (Postfix, from userid 110) id E5E1F29A3B; Wed, 23 Oct 2002 14:53:26 -0400 (EDT)
Received: from [63.104.212.252] by xprdmailfe23.nwk.excite.com via HTTP; Wed, 23 Oct 2002 14:53:26 EST
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0
MIME-Version: 1.0
X-Sender: dgoodspe@excite.com
X-Mailer: PHP
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <20021023185326.E5E1F29A3B@xmxpita.excite.com>
Date: Wed, 23 Oct 2002 14:53:26 -0400
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Don Goodspeed <dgoodspe@EXCITE.COM>
Subject: Re: Comments on draft-katz-yeung-traffic-08.txt
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

With these changes, I have no further issues.  Looks good!.
-don

 --- On Wed 10/23, Acee Lindem  wrote:
From: Acee Lindem [mailto: acee@REDBACK.COM]
To: OSPF@DISCUSS.MICROSOFT.COM
Date: Wed, 23 Oct 2002 14:22:39 -0400
Subject: Re: Comments on draft-katz-yeung-traffic-08.txt

> Sounds good to me.
>
> Kireeti Kompella wrote:
>
> > Hi Acee,
> >
> > On Tue, 22 Oct 2002, Acee Lindem wrote:
> >
> >
> >>I don't expect to have any comments on IETF wide last call.
> >>
> >
> > Can I hold you to that?  :-)
> >
> >
> >>>This is a nitpick.
> >>>
> >>Have you ever met a programmer who didn't?
> >>
> >
> > None that I respect :-)
> >
> >
> >>I was just thinking that a document going to proposed standard
> would
> >>be better served with a single way of handling multi-access links.
> If
> >>I'm the only one with this concern then I'll relent.
> >>
> >
> > It wouldn't be better served changing something *that works and
> > interoperates* at the last minute.
> >
> > New wording (the part after the semicolon is new):
> >
> > | If the Link Type of the link is Multiaccess, the Remote
> > | Interface IP Addess is set to 0.0.0.0; alternatively, an
> implementation
> > | MAY choose not to send this sub-TLV.
> >
> >
> >>>However, if you think that the new wording is preferable, I
> will
> >>>change this to "Operation over multiaccess links with
> more than two
> >>>devices is not specifically prohibited.  More accurate
> description of
> >>>the reservation state of multi-access networks is for further
> study."
> >>>
> >>
> >>There was considerable discussion on this topic and I believe
> >>this a good addition.
> >>
> >
> > Done.  New wording:
> >
> > | The reservation state of multiaccess
> > | links may not be accurately reflected, except in the special case
> that
> > | there are only two devices in the multiaccess subnetwork.
> Operation
> > | over multiaccess networks with more than two devices is not
> specifically
> > | prohibited.  More accurate description of the reservation state of
> > | multi-access networks is for further study.
> >
> > Note one other minor change: "reservation state ... is not
> ..." to
> > "reservation state ... may not be ..."
> >
> > Can we ship this out now?
> >
> > Kireeti.
> >
> >
>
>
> --
> Acee
>

_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!