[BXXPwg] Last Call: The Blocks Extensible Exchange Protocol Frameworkto Proposed Standard

Marshall T. Rose mrose+mtr.netnews@dbc.mtview.ca.us
Tue, 21 Nov 2000 09:38:54 -0800


it's a typo: s/119/132/

/mtr

----- Original Message -----
From: "Ward K Harold" <ward.harold@tivoli.com>
To: <bxxpwg@invisible.net>
Sent: Tuesday, November 21, 2000 02:17
Subject: Re: [BXXPwg] Last Call: The Blocks Extensible Exchange Protocol
Frameworkto Proposed Standard


> I realize this is a nit but I noticed that in section 2.2 the payload
> size stated in the text and in the example frame disagree. The text says
> the frame "contains a payload of 119 octets". The example shows a size
> parameter of 132. When I cut the payload out and ran it through 'wc' I
> got 133 characters (octets?) but emacs may have added a character
> somewhere.
>
> ... WkH
>
> The IESG wrote:
>
> > The IESG has received a request from the Blocks Extensible Exchange
> > Protocol Working Group to consider publication of the following as
> > Proposed Standards:
> >
> > o The Blocks Extensible Exchange Protocol Framework
> >         <draft-ietf-beep-framework-08.txt>
> > o Mapping the BXXP Framework onto TCP
> >         <draft-ietf-beep-tcpmapping-04.txt>
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action.  Please send any comments to the
> > iesg@ietf.org or ietf@ietf.org mailing lists by December 4, 2000.
> >
> > Files can be obtained via
> > http://www.ietf.org/internet-drafts/draft-ietf-beep-framework-08.txt
> > http://www.ietf.org/internet-drafts/draft-ietf-beep-tcpmapping-04.txt
> >
> > _______________________________________________
> > BXXPwg mailing list
> > BXXPwg@lists.invisible.net
> > http://lists.invisible.net/mailman/listinfo/bxxpwg
>
>
> _______________________________________________
> BXXPwg mailing list
> BXXPwg@lists.invisible.net
> http://lists.invisible.net/mailman/listinfo/bxxpwg
>