Re: [Lsvr] Adoption of draft-ymbk-lsvr-l3dl-(signing|ulpc)

[Randy Bush <[e-mail]>]

thanks for the support

> I *do* think that the last paragraph in Security Considerations of
> ulpc should remain as is though,...

:)

> "Any keying material in the PDU SHOULD BE salted ad hashed." - "and".

thanks

> A: I suspect that there are missing attributes that should be added,
> but I cannot think of any critical ones.

i admit to guilt-free obsessive minimalism

> B: I'm not 100% sure what the relationship is between this and the IDR
> BGP AutoConf work is - this looks like it provides much of the
> building blocks that the IDR work might use, but where is the line
> between them?

ships in the night

but i agree that this is useful as an example in the idr-dt.  fwiw, i
have queued homework over there.

> C: It feels like more text is needed around "If a peering address has
> been announced as a loopback, a two or three (one or both ends could
> be loopbacks) hop
>    BGP session will be established. " -- how do I know it is announced
> as a loopback? How do I know what route to install to reach the
> loopback? etc.

l3dl 13.2 tells you it is a loopback

13.2.  Encapsulaion Flags

   The Encapsulation Flags are a sequence of bit fields as follows:

    0           1            2            3            4  ...       7
   +------------+------------+------------+------------+------------+
   |  Ann/With  |   Primary  | Under/Over |  Loopback  | Reserved ..|
   +------------+------------+------------+------------+------------+

so how about

   For each BGP peering on a link here MUST be one agreed encapsulation,
   and the addresses used MUST be in the corresponding L3DP IPv4/IPv6
   Announcement PDUs.  If a peering address has been announced as a
   loopback, i.e. MUST BE flagged as such in the L3DL Encapsulation PDU,
   a two or three hop BGP session will be established.  Otherwise a
   direct one hop session is used.

needs 2119 language MUST HAVE BEEN :)

randy