draft-ietf-pim-join-attributes-01 draft-ietf-pim-rpf-vector-02

1
draft-ietf-pim-join-attributes-01
draft-ietf-pim-rpf-vector-02

• Arjen Boers, Cisco Systems
• IJsbrand Wijnands, Cisco Systems
• Eric Rosen, Cisco Systems

65st IETF Dallas March 2006
2
Agenda

• Attributes draft
• History
• Lastcall Comments / changes
• Vector draft
• Changes
• Status

3
draft-ietf-pim-join-attributes-01History

• Started out as one draft that described
• General encoding format
• RPF-Vector
• RPF-Vector-stack
• RPF-VectorRD for inter-AS MVPN deployment as
  described in draft-rosen-vpn-mcast-08
• Based on WG comments
• Documented general encoding in separate draft
• Draft-ietf-pim-join-attributes
• Documented RPF-Vector in separate draft
• Draft-ietf-pim-rpf-vector
• Removed Vector-Stack and VectorRD at all

4
draft-ietf-pim-join-attributes-01Lastcall
comments

• Rephrased and clarified some sections, added
  security section / iana considerations

• Received more comments after lastcall, mainly
  related to conflict resolution

5
draft-ietf-pim-rpf-vector-02Changed
PIM RPF vector Attribute encoding
0 1 2
3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7
8 9 0 1 2 3 4 5 6 7 8 9 0 1 -----------
--------------------- FS
Type Length IP
address ---------------------
--------.......
to
0 1 2
3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
-------------------------
------- FS Type Length
Encoded-Unicast address
-------------------------
----.......
6
Draft status

• Join-attributes draft without application is
  not useful
• Alternative proposal by Tom for Vector draft
  mentioned during Vancouver IETF
• Not published
• How to proceed with Vector draft ?