[alto] Some questions for alto-cdni-request-routing

[Shawn Lin <[e-mail]>]

Dear authors of  draft-ietf-alto-cdni-request-routing-alto-00 and ALTOers,


Using ALTO to provide guidelines on the FCI protocol is really a good
idea since ATLO can provide resources information of network as well as
endpoints by an elegant way.


1. I found that there are *two sections (3.3.2 and 3.3.3) left blank *in
this draft, have they be solved yet?

2. It seems that *how to use ALTO network map* is not described in this
draft.


I posted one example and its source for each of them, and hope we can refresh
the current progress and try to move it forward.


*3.3.2.  Incremental FCI Update Example*

source:
https://datatracker.ietf.org/meeting/99/materials/slides-99-alto-cdni-footprint-and-capabilities-advertisements-using-alto/


POST /updates/fci HTTP/1.1

Host: fcialtoupdate.example.com

Accept: text/event-stream,application/alto-error+json Content-Type:
application/alto-updatestreamparams+json Content-Length: ###

{ "add": {

    "my-fci-stream": {

        "resource-id": "my-fci-map"

    }

}


HTTP/1.1 200 OK

Connection: keep-alive

Content-Type: text/event-stream

event: application/alto-updatestreamcontrol+json

data: {"control-uri": "
http://fcialtocu.example.com/updates/streams/3141592653589"}


event: application/cdni,my-fci-stream

data: { ... full cdni message ... }


event: application/merge-patch+json,my-fci-stream

data: { ... Merge patch update of cdni objects ... }


event: application/json-patch+json,my-fci-stream

data: { ... JSON patch update of cdni objects, e.g., footprints entries ...
}


*3.3.3.  FCI Using ALTO Network Map Example*

source: https://tools.ietf.org/html/draft-ma-cdni-capabilities-09#section-5


networkmap:

    GET /networkmap HTTP/1.1

    Host: http://alto.example.com/fcifootprint001

    Accept: application/alto-networkmap+json,application/alto-error+json


    HTTP/1.1 200 OK

    Content-Length: 319

    Content-Type: application/alto-networkmap+json


    {

      "meta" : {

        "vtag": [

          {"resource-id": "my-eu-netmap",

           "tag": "1266506139"

          }

        ]

      },

      "network-map" : {

        "south-france" : {

          "ipv4" : [ "192.0.2.0/24", "198.51.100.0/25" ]

        },

        "germany" : {

          "ipv4" : [ "192.0.3.0/24"]

        }

      }

    }


fcimap:

      GET /fcimap HTTP/1.1

      Host: alto.example.com

      Accept: application/alto-fcimap+json,application/alto-error+json


      HTTP/1.1 200 OK

      Content-Length: 618

      Content-Type: application/alto-fcimap+json


      {

        "meta" : {

        },

        "fcimap": {

          "capabilities": [

            { "capability-type": "FCI.DeliveryProtocol",

              "capability-value": [

                "http1.1"

              ]

            },

            { "capability-type": "FCI.DeliveryProtocol",

              "capability-value": [

              "values": [

                "https1.1"

              ],

              "footprints": [

                { "footprint-type": "altonetworkmap",

                  "footprint-value": [

*                    "http://alto.example.com/fcifootprint001
<http://alto.example.com/fcifootprint001>",*

*                    "germany",*

*                    "south-france"*

                  ]

                }

              ]

            }

          ]

        }

      }


One suggestion about the "footprint-value": although the meaning of each
element in "footprint-value" list is described in
draft-ma-cdni-capabilities-09, it may be better to use objects in
"footprint-value" list in some circumstances. For example, this may be more
human readable.

"footprint-value": [

  {"uri": *"http://alto.example.com/fcifootprint001
<http://alto.example.com/fcifootprint001>*"},

  {"country":"*germany*"},

  {"coutry":"*south-france*"}

]


Bests,

X. Shawn Lin