[BXXPwg] Profile or Profiles? Is it too late for edits?

Marshall T. Rose mrose+mtr.netnews@dbc.mtview.ca.us
Sun, 28 Jan 2001 23:04:31 -0800


This is a multi-part message in MIME format.

------=_NextPart_000_009D_01C0897E.AC3DA6A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> Is it too late for edits?

probably. we've already had two working group last calls and an extended
iesg last call. other than the punctuation typo you mention, i'm disinclined
to argue with the rfc editor to hold the presses and get everyone to agree
to the changes...

/mtr
  ----- Original Message -----
  From: Bob Wyman
  To: bxxpwg@lists.invisibleworlds.com
  Sent: Thursday, January 25, 2001 10:29
  Subject: [BXXPwg] Profile or Profiles? Is it too late for edits?


  Is it too late for edits?

  Section 2 of draft-ietf-beep-framework-11.txt says:
  "When a session is established, each BEEP peer advertises the profile it
supports."
  Shouldn't this sentence have referred to "profiles" (i.e. plural?).

  Also, it would appear from 2.3.1.1 that peers only advertise the profiles
that they support while acting in a server role. This distinction is not
made in this text. Given these two observations, I would suggest that the
sentence in Section 2 would read better as:
  "When a session is established, each BEEP peer advertises the profile[s]
it supports [when acting in a server role]."

  Section 2.3 says:
  "Channel management allows each BEEP peer to advertise the profiles that
it supports..."
  This sentence may have a problem similar to the one in Section 2.,
although it isn't stating a requirement -- only reflecting on the purposes
of channel management. It might read better as:
  "Channel management allows each BEEP peer to advertise the profiles that
it supports [when acting in a server role]...."

  Also, I'm curious, other than the "TASK=0" of DECnet, I can't think of any
other protocol that works the way BEEP does in that the protocol or profile
is specified after the connection is made. Please forgive me if I'm missing
something obvious. Can anyone provide other examples?

          bob wyman


------=_NextPart_000_009D_01C0897E.AC3DA6A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>&gt; Is it too late for =
edits?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>probably. we've already had two working =
group last=20
calls and an extended iesg last call. other than the punctuation typo =
you=20
mention, i'm disinclined to argue with the rfc editor to hold the =
presses and=20
get everyone to agree to the changes...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>/mtr</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dbobwyman@earthlink.net =
href=3D"mailto:bobwyman@earthlink.net">Bob=20
  Wyman</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
  title=3Dbxxpwg@lists.invisibleworlds.com=20
  =
href=3D"mailto:bxxpwg@lists.invisibleworlds.com">bxxpwg@lists.invisiblewo=
rlds.com</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, January 25, =
2001=20
  10:29</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [BXXPwg] Profile or =
Profiles? Is=20
  it too late for edits?</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>Is it too late for =
edits?</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Section 2 of =
draft-ietf-beep-framework-11.txt=20
  says:<BR>"When a session is established, each BEEP peer advertises the =
profile=20
  it supports."</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Shouldn't this sentence have referred =
to=20
  "profiles" (i.e. plural?). </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Also, it would appear from 2.3.1.1 =
that peers=20
  only advertise the profiles that they support while acting in a server =
role.=20
  This distinction is not made in this text. Given these two =
observations, I=20
  would suggest that the sentence in Section 2 would read better=20
as:</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>"When a session is established, each =
BEEP peer=20
  advertises the profile[s] it supports [when acting in a server=20
  role]."</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Section 2.3 says:</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>"Channel management allows each BEEP =
peer to=20
  advertise the profiles that it supports..."</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>This sentence may have a problem =
similar to the=20
  one in Section 2., although it isn't stating a requirement -- only =
reflecting=20
  on the purposes of channel management. It might read better =
as:</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>"Channel management allows each BEEP =
peer to=20
  advertise the profiles that it supports [when acting in a server=20
  role]...."</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Also, I'm curious, other than the =
"TASK=3D0" of=20
  DECnet, I can't think of any other protocol that works the way BEEP =
does in=20
  that the protocol or profile is specified after the connection is =
made. Please=20
  forgive me if I'm missing something obvious. Can anyone provide other=20
  examples?</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bob=20
  wyman</FONT></DIV>
  <DIV><FONT face=3DArial =
size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_009D_01C0897E.AC3DA6A0--