Opened 7 years ago

Last modified 7 years ago

#2 new enhancement

Identify l3vpn svc using id or name or both?

Reported by: bill.wu@… Owned by: draft-ietf-l3sm-l3vpn-service-model@…
Priority: minor Milestone:
Component: l3vpn-service-model Version:
Severity: - Keywords: string int32
Cc:

Description

In the (v-01), l3vpn svc can be identified by both name and id, both name and id are unique and internal reference for VPN service,id is optional parameter while name is mandatory parameter and key for vpn service.

Scharf Michael believed that id is redundant and suggested to use name only.

The relevant question is who generate these identifier? user or system, when we choose to use int32 as data type for id, why not use UUID since
UUID is 128bits long generated by system, common data type defined in RFC6991 and is an identifier that is unique across both space and time. but UUID should depend on specific generation algorithm and follow specific format.

Change History (2)

comment:1 Changed 7 years ago by bill.wu@…

  • Component changed from draft-ltsd-l3sm-l3vpn-service-model to l3vpn-service-model
  • Owner changed from draft-ltsd-l3sm-l3vpn-service-model@… to draft-ietf-l3sm-l3vpn-service-model@…

comment:2 in reply to: ↑ description Changed 7 years ago by bill.wu@…

There was agreement on the list to use name only to get in line with other properties defind in the service model.

Replying to bill.wu@…:

In the (v-01), l3vpn svc can be identified by both name and id, both name and id are unique and internal reference for VPN service,id is optional parameter while name is mandatory parameter and key for vpn service. The change we need for service model is to remove vpn-svc id from service model.

Scharf Michael believed that id is redundant and suggested to use name only.

The relevant question is who generate these identifier? user or system, when we choose to use int32 as data type for id, why not use UUID since
UUID is 128bits long generated by system, common data type defined in RFC6991 and is an identifier that is unique across both space and time. but UUID should depend on specific generation algorithm and follow specific format.

Note: See TracTickets for help on using tickets.