Re: [sidr] bgpsec-spec S. 4.2 comments

[Randy Bush <[e-mail]>]

> The discussion here (and John's comment) is related to text in Section
> 4.2, where we discuss what a BGPSEC router does when "propagating" a
> route advertisement.  "Propagating" connotes here that the update (or
> route) was received from an eBGP peer.

not exactly.  4.0 says

   Sections 4.1 and 4.2 cover two cases in which a BGPSEC speaker may
   generate an update message containing the BGPSEC_Path_Signatures
   attribute.  The first case is that in which the BGPSEC speaker
   originates a new route advertisement (Section 4.1).  That is, the
   BGPSEC speaker is constructing an update message in which the only AS
   to appear in the AS_PATH attribute is the speaker's own AS (normally
   appears once but may appear multiple times if AS prepending is
   applied).  The second case is that in which the BGPSEC speaker
   receives a route advertisement from a peer and then decides to
   propagate the route advertisement to an external (eBGP) peer (Section
   4.2).  That is, the BGPSEC speaker has received a BGPSEC update
   message and is constructing a new update message for the same NLRI in
   which the AS_PATH attribute will contain AS number(s) other than the
   speaker's own AS.