[P2PSIP] Route Logging in RELOAD

[Jaime Jimenez]

Hi,

I have a question about the Forwarding Header of RELOAD, particularly 
the Route Logging.


      enum { (255) } RouteLogExtensionType;

      struct {
        RouteLogExtensionType     type;
        uint16                    length;

        select (type){
          /* Extension values go here */
        } extension;
      } RouteLogExtension;

      enum {
         reserved(0),
         tcp_tls(1),
         udp_dtls(2),
         (255)
      } OverlayLink;

      struct {
        opaque                 version<0..28-1>;    /* A string */
        OverlayLink            linkProtocol;            /* TCP or UDP */
        NodeId                 id;
        uint32                 uptime;
        IpAddressPort          address;
        opaque                 certificate<0..216-1>;
        RouteLogExtension      extensions<0..216-1>;
      } RouteLogEntry;

      struct {
         RouteLogEntry         entries<0..216-1>;
      } RouteLog;


The structure defines a RouteLogExtension but I could not interprete 
whether it defines many extensions for each RouteLogEntry or just one.

In the case there are many we have a problem when we parse an encoded 
message since we do not know the length of the RouteLogExtension 
structure or the number of extensions there are. So, if there were many, 
it might be convenient to have a field specifying the length of the list 
of entries.

Thanks, Jaime Jiménez.
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip