About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: Help Please - Reducing Routes (fwd) just for info

  • To:
  • From:
  • Date: Mon, 11 Mar 96 19:16:45 +0300












>   >From <@ncc.ripe.net:owner-routing-wg@localhost Fri Mar  8 17:00:04 1996
>   Message-Id: <9603081340.AA02991@localhost>
>   To: RIPE Routing WG routing-wg@localhost,
>           European ISP Forum eof-list@localhost
>   Subject: Help Please - Reducing Routes
>   Cc: RIPE NCC Staff staff@localhost
>
Yes, it's understandable. But I'd like to make a notes:

1) It's better to produce some information in Subject:,
as (The_number_of_redundant_networks)

2) Subject is not understandable.

3) May be it's better to change message structure:

I. Short reference:
(For example):

 Below is the list of redundant networks anounced by you routers.
 See detail descriprion below (after ---END line).
---(BEGIN)
...
...
...
---(END)

 == Detail description ==.

This is because usially all system administrators know good all this description
(after they'll read it first). Some networks would be redundant always due to
different reasons (technical and political), that means this messages would
be received fast enougph. It's important this case to see news list of
networks just in the message beginning; moreover, may be somebody would have
some robot to execute this messages. That's why I prefere to have
description in the end of the message, and to mark main part of this
message by some special lines (---(BEGIN), ---(END) , for example).
--- 
Aleksei Roudnev, Network Operational Centre, Relcom, Moscow
(+7 095) 194-19-95 (Network Operational Centre Hot Line)
(+7 095) 196-72-12 (Support), (+7 095) 194-33-28 (Fax)




  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community