close Warning: Can't synchronize with repository "(default)" ("(default)" is not readable or not a Git repository.). Look in the Trac log for more information.

Changes between Version 1 and Version 2 of Proto/aArchitecture/MFPacket


Ignore:
Timestamp:
Nov 30, 2014, 4:34:52 AM (9 years ago)
Author:
wontoniii
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Proto/aArchitecture/MFPacket

    v1 v2  
    11== Format ==
    22
    3 The following is the bitwise structure for a MobilityFirst packet:
     3The following is the bitwise structure for a !MobilityFirst packet:
    44
    55{{{
    … …  
    3939}}}
    4040
    41 * '''Version''' - MobilityFirst network protocol version encoded as ''major.minor'' (4-bits each)
     41* '''Version''' - !MobilityFirst network protocol version encoded as ''major.minor'' (4-bits each)
    4242* '''Service type ''' - Encodes requested processing or delivery service(s); MSB of '1' indicates presence of one or more extension headers following the fixed header fields.
    4343* '''Protocol''' - Upper protocol identifier
    … …  
    5757== Service Type (ST) ==
    5858
    59 The table below lists the 16-bit values designated for 'basic' services in MobilityFirst network protocol. It is not expected that each network element support all of these services, and may either choose to ignore unsupported services (when makes sense) or report back a failure to packet originator.
     59The table below lists the 16-bit values designated for 'basic' services in !MobilityFirst network protocol. It is not expected that each network element support all of these services, and may either choose to ignore unsupported services (when makes sense) or report back a failure to packet originator.
    6060
    6161|| '''Network service''' || '''ST value''' || '''Description''' ||
    … …  
    167167
    168168* '''Compute Service GUID''' - GUID of the compute plane service to be invoked on the payload
    169 * '''Arguments/Results Count''' - number of arguments and number of results (post processing) to and from the processing of the payload. This is besides any changes to the payload itself. TBD - if the payload changes in some way (e.g., size, checksum) the results should indicate these changes so stack layers may take it into consideration when validating the payload.
     169* '''!Arguments/Results Count''' - number of arguments and number of results (post processing) to and from the processing of the payload. This is besides any changes to the payload itself. TBD - if the payload changes in some way (e.g., size, checksum) the results should indicate these changes so stack layers may take it into consideration when validating the payload.
    170170* '''Compute Service Arguments''' - arguments in TLV, for instance, with pre-defined types and length for each argument expected by the compute service.
    171171* '''Compute Service Results''' - results encoded in TLV, for instance, with pre-defined types well known to the routing layer. These results may chiefly help the routing/transport layers to understand changes to the payload