Subject: Issue 32.1

From: "Natale, Jonathan" <[email-masked]>
Date: Thu, 3 Oct 2002 12:04:44 -0400

Folks,

Here is an example of a confused person (see bellow).  AGAIN, I propsed we

CHANGE:

   "ORIGIN is a well-known mandatory attribute. The ORIGIN attribute
   is generated by the BGP speaker that originates the associated BGP
   routing information. The attribute shall be included in the UPDATE
   messages of all BGP speakers that choose to propagate this information
   to other BGP speakers."
(--current consensus(???), if I send the above to this person
he may still be confused)

TO:

   "ORIGIN is a well-known mandatory attribute. The ORIGIN attribute
   shall be generated by the speaker that originates the
   associated routing information. Its value should not be
   changed by any other speaker unless the other speaker is
   administratively configured to do so to affect policy
   decisions."

-or-

   "ORIGIN is a well-known mandatory attribute. The ORIGIN attribute
   shall be generated by the speaker that originates the
   associated routing information. Its value should not be
   changed by any other speaker."

Example Confused Person (sorry for making an example out of you, Mallika):

-----Original Message-----
From: mallika gautam [mailto:[email-masked]] 
Sent: Thursday, October 03, 2002 4:29 AM
To: [email-masked]
Subject: [isp-bgp] Origin value as EGP

Hi All,
The origin attribute takes values as IGP, EGP or
Incomplete. According to the text given on this topic,
IGP is when the path information is originated within
an AS. EGP, when it is learned from some other AS and Incomplete, when the
information is learnt by other means. A very elementary qn. in this regards
is whether the update coming from an EBGP peer have the origin field as EGP,
if the sending AS comes to know about this path from some 3rd AS. 

ie. 

ASN 100 learns a path from ASN 200 and then ASN 100
sends it to ASN 300. Then will the path which ASN 300
finally receive from ASN 100 has the origin attribute
as EGP.

If this is not true then can anybody pl. suggest a
scenerio when the route information will have EGP as
the origin field value.

Thanks
Mallika

(Note:  This also disproves the contention that RFCs are for DE's
[only]--they are also for CE's, SE's, QE's, FE's, etc...