Re: RFC Editor RFP Review Request

["todd glassey" <tglassey at earthlink.net>]

Elliot -
Then you leave it up to the party providing the service and open the IETF to
all kinds of trouble... By the way Elliot do you think your sponsor, Cisco
and their Legal department would let Cisco negotiate a contract like that?
Just curious


But hey - Maybe - try something like this:

    1)    as part of the Document Publishing function, "RFC Editors"will
operate document distribution, access, and delivery services on the
Internet; these services to be provided in compliance with the agreed upon
terms and conditions as defined in this Service Level Agreement. These
services are to be available to any and all  and as a minimum the following
servers/protocol's are necessary:

    o- http for Web based Browsing and BOT based recovery
    o- ftp for ftp, wget, curl clients implementing a bare set of FTP
Services
    o- rsync or mirror protocols for site-mirroring and selective recovery
of changes to the portfolio offered in the Document Publication Server
site(s).
    o- Email based Document Notification and Recovery

[Comment: Protocols to be served, and their available bandwidth's and
availability/fail-over's would all have to be in compliance with an SLA to
be negotiated with the ISOC/Secretariat in the awarding of the service
agreement. This SLA should be disclosed as well to the Body of the
Membership of the IETF at the completion of the negotiations as well as part
of the Open and Fair part of the managing of the IETF.]

    2)    An official IETF RFC Editor Mirror Program is to be established
allowing Mirrors to formally register with the RFC Editors and to provide 'a
formalized agreement to mirror the IETF media suite in one or more of its
publication forms'. Officially sanctioned sites must agree to the IETF's SLA
for 'Operating an Official IETF Mirror Site' which gives the IETF tremendous
control on those sites formalized as official mirrors who mirror its
content. Official Mirrors of the Master Document Archive will be made over
secure channels and as such will require formal registration and management
of the accounts.

[Comment: Hey SOB - this is the document I was referring to  - the plan for
how an 'official mirror' is created and what its operating requirements are.
The magic here is that any number of the VENDORS may want to operate their
own commercial mirrors and that also could be a source of revenue for the
TRUST - either way some SLA is needed.]

T

----- Original Message ----- 
From: "Eliot Lear" <lear at cisco.com>
To: "Henrik Levkowetz" <henrik at levkowetz.com>
Cc: <iad at ietf.org>; <iab at ietf.org>; <ietf at ietf.org>; <iaoc at ietf.org>;
<paul.hoffman at vpnc.org>; "Bob Braden" <braden at ISI.EDU>; <iesg at ietf.org>
Sent: Saturday, July 22, 2006 12:21 AM
Subject: Re: RFC Editor RFP Review Request


> Henrik Levkowetz wrote:
> > So how would you specify the requirement to provide rsync
> > functionality in the SOW?
> >
> >
>
> I would think you would say something like, "The RFC Editor shall make
> available an archive of RFCs in ways most convenient to both active
> participants and casual observers" and leave it at that.
>
> _______________________________________________
> Ietf mailing list
> Ietf at ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf