IPP Mail Archive: RE: IPP> RFC 3080/3081 - BEEP (Blocks Exte

IPP Mail Archive: RE: IPP> RFC 3080/3081 - BEEP (Blocks Exte

RE: IPP> RFC 3080/3081 - BEEP (Blocks Extensible Exchange Protoco l)

From: Manros, Carl-Uno B (cmanros@cp10.es.xerox.com)
Date: Mon Mar 05 2001 - 11:51:38 EST

  • Next message: don@lexmark.com: "RE: IPP> RFC 3080/3081 - BEEP (Blocks Extensible Exchange Protoco l)"

    Ned,

    In response, I think you will find that our more recent documents have
    become shorter (but instead more of them).

    I think you failed to reveal to us that doing the drafts in NROFF could have
    cut the IESG/RFC Editor process with some 12 months or so...

    Carl-Uno

    Carl-Uno Manros
    Manager, Print Services
    Xerox Architecture Center - Xerox Corporation
    701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231
    Phone +1-310-333 8273, Fax +1-310-333 5514
    Email: manros@cp10.es.xerox.com

    -----Original Message-----
    From: ned.freed@mrochek.com [mailto:ned.freed@mrochek.com]
    Sent: Saturday, March 03, 2001 2:03 PM
    To: McDonald, Ira
    Cc: 'ipp@pwg.org'
    Subject: Re: IPP> RFC 3080/3081 - BEEP (Blocks Extensible Exchange
    Protocol)

    > So the BEEP stuff is now IETF Proposed Std RFC 3080/3081.

    > Amazing how quickly things can move in the RFC Editor's queue.

    I've found that things move a lot quicker when (1) You provide NROFF source
    to
    the RFC editor and (2) The documents are relatively short and use relatively
    simple typographical conventions. I believe the BEEP documents met all of
    these criteria.

    I pointed this out to the IPP WG at one point but was told that this wasn't
    an
    option for IPP documents.

                                            Ned



    This archive was generated by hypermail 2b29 : Mon Mar 05 2001 - 11:53:03 EST