Hello, We would like to see some discussion on the list for draft-arango-pim-join-attributes-for-lisp. The LISP multicast specification in RFC6831 defaults to the use of a multicast transport over RLOC space. The draft introduces two new attributes to PIM signaling to support unicast transport with ingress replication. Slides describing the proposal can be found at: http://www.ietf.org/proceedings/86/slides/slides-86-lisp-8.pptx
Unicast transport requires the communication of two additional pieces of information in the PIM(S-EID,G)Join message: 1) An indication that the receiver-ETR wants unicast transport and is not additionally joining through native multicast by sending an (S-RLOC,G) Join. 2) The receiver-ETR RLOC address that should be used as the destination for the LISP unicast encapsulated multicast data packets. The draft is introducing the "Transport" and "Receiver RLOC" PIM Join/Prune attributes to carry the additional required information in LISP encapsulated (S-EID,G) Join/Prune PIM messages. The draft was presented in Orlando in the PIM working group but due to agenda time limitations it was not presented in LISP. The conclusion in the PIM WG is that they have no problem in adopting the draft as long as the LISP WG thinks that it makes sense and is useful. We are therefore looking for input to move this forward. Note that the draft is incorrectly labeled as standards track. It will be fixed to reflect that it is experimental in the next revision. thanks Isidor _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
