Browse Prior Art Database

Scheduled network software maintenance (RFC0440)

IP.com Disclosure Number: IPCOM000003596D
Original Publication Date: 1973-Jan-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 1 page(s) / 2K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D.C. Walden: AUTHOR

Abstract

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.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 100% of the total text.

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.

*An IMP-GOING-DOWN-FOR-SCHEDULED-SOFTWARE-MAINTENANCE message.

[ 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 ]