@techreport{ravi-ccn-forwarding-label-02,
    number =    {draft-ravi-ccn-forwarding-label-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ravi-ccn-forwarding-label/02/},
    author =    {Ravi Ravindran and Asit Chakraborti and Aytac Azgin},
    title =     {{Forwarding-Label support in CCN Protocol}},
    pagetotal = 16,
    year =      2016,
    month =     mar,
    day =       21,
    abstract =  {The objective of this proposal is to enable ID and Locator namespace split in the CCN protocol that has several applications such as towards Interest routing optimization, mobility, handling indirections in manifests, and routing scalability. We enable this through the notion of forwarding-label (FL) object, which is an optional hop-by-hop payload in the Interest message with a locator name which identifies a network domain, router, or a host. Depending on the application and trust context, an FL object can be subjected to policy based actions by the forwarders such as invoking security verification or enabling other service-centric actions such as FL object replacement. FL object can be inserted by the applications or by the network. To enable dynamic name resolution FL objects can also be modified in the network by designated points such as the edge routers.},
}