[BXXPwg] Re: WG Review: Blocks eXtensible eXchange Protocol (bxxpwg)
Mon, 19 Jun 2000 21:43:13 -0700
hi. i'm not sure i'm clear on what you're saying.
my reading of the proposed charter says that we start with the bxxp draft,
which provides fundamental support for both privacy and authentication
it's true that the charter references an early version of the i-d, but it's
not something that i can get worked up over. i imagine that the working
group, if chartered, will probably produce a couple of drafts before it goes
to the iesg.
so, what am i missing in your concern?
----- Original Message -----
From: Kurt D. Zeilenga <Kurt@OpenLDAP.org>
To: The IESG <email@example.com>
Cc: <firstname.lastname@example.org>; <email@example.com>
Sent: Monday, June 19, 2000 10:47
Subject: [BXXPwg] Re: WG Review: Blocks eXtensible eXchange Protocol
> I am generally supportive of this proposed working group
> being approved. I suggest, however, that the charter be
> amended to explicitly require that the resulting framework
> support strong authentication and security services. The
> current charter implies such are required per the blocks
> reference. However, given that the blocks I-D will likely
> expire long before this working group submits an I-D for
> IESG review (in fact 03 no longer exists in the repository
> due to subsequent revision), such key requirements such
> as this should be made explicit.
> At 01:03 PM 6/19/00 -0400, The IESG wrote:
> >A new IETF working group has been proposed in the Applications Area.
> >The IESG has not made any determination as yet.
> >The following Description was submitted, and is provided for
> >informational purposes only:
> >Blocks eXtensible eXchange Protocol (bxxpwg)
> > Mailing Lists:
> > General Discussion:firstname.lastname@example.org
> > To Subscribe: email@example.com
> > Archive: http://lists.invisible.net/pipermail/bxxpwg/
> >Description of Working Group:
> >The IETF BXXP working group shall develop a standards-track application
> >protocol framework for connection-oriented, asynchronous
> >request/response interactions.
> >The framework must permit multiplexing of independent request/response
> >streams over a single transport conneciton, supporting both textual and
> >binary messages.
> >The working group shall use BXXP (as described in
> >draft-mrose-blocks-protocol-03) as its starting point. The working group
> >is authorized to make incompatible changes to BXXP providing that it
> >document solid technical reasons for doing so.
> BXXPwg mailing list