IT. Expert System.

RFC (unknown status)

Scheduled network software maintenance. D.C. Walden. January 1973. RFC440. (Format: TXT=1870 bytes) (Status: UNKNOWN) (DOI: 10.17487 / RFC440)

 Network Working Group                                    David C. Walden
RFC #440                                                 BBN-NET
NIC #13772                                               January 1973
Updates: 381,406
                 Scheduled Network Software Maintenance
    As explained in RFC 381, we believe that we can minimize
the disruption caused by the release of new IMP software systems by
doing them on a regularly scheduled basis.  In the past we have
reserved the one hour period from 7am until 8am every Tuesday morning
for our IMP system scheduled software maintenance period.  As the size
of the network has grown to about forty IMPs, we find we can no longer
complete a system release to all IMPs in the one hour scheduled.
Therefore, we are extending our scheduled software maintenance period
to two hours from 7am until 9am eastern time every Tuesday
morning. The extended period will take effect as of the first Tuesday
in February.  As we said in RFC 381, we will not always use the
Tuesday morning period, but we always reserve it.  On Tuesday mornings
when we _do_ use the scheduled software maintenance period, a type 2 IMP
to Host message* will be sent to all Hosts about an hour in advance of
the period.
    We understand that the software maintenance period cannot
continue to grow linearly with the number of IMPs, and we will find a
way around this problem before software releases start taking 168
hours a week.
       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by Alex McKenzie with    ]
       [ support from GTE, formerly BBN Corp.             9/99 ]
Walden                                                          [Page 1] 


Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)





Java Script








Design patterns

RFC (standard status)

RFC (proposed standard status)

RFC (draft standard status)

RFC (informational status)

RFC (experimental status)

RFC (best current practice status)

RFC (historic status)

RFC (unknown status)

IT dictionary

All information of this service is derived from the free sources and is provided solely in the form of quotations. This service provides information and interfaces solely for the familiarization (not ownership) and under the "as is" condition.
Copyright 2016 © ELTASK.COM. All rights reserved.
Site is optimized for mobile devices.
Downloads: 145 / 158763809. Delta: 0.00326 с