{"action":"opened","issue":{"url":"https://api.github.com/repos/alreadytiredofnomcom/L2SMissues/issues/38","repository_url":"https://api.github.com/repos/alreadytiredofnomcom/L2SMissues","labels_url":"https://api.github.com/repos/alreadytiredofnomcom/L2SMissues/issues/38/labels{/name}","comments_url":"https://api.github.com/repos/alreadytiredofnomcom/L2SMissues/issues/38/comments","events_url":"https://api.github.com/repos/alreadytiredofnomcom/L2SMissues/issues/38/events","html_url":"https://github.com/alreadytiredofnomcom/L2SMissues/issues/38","id":178591863,"number":38,"title":"Add 1R2C and 2R3C options to \"class-of-service\"?","user":{"login":"alreadytiredofnomcom","id":13851444,"avatar_url":"https://avatars.githubusercontent.com/u/13851444?v=3","gravatar_id":"","url":"https://api.github.com/users/alreadytiredofnomcom","html_url":"https://github.com/alreadytiredofnomcom","followers_url":"https://api.github.com/users/alreadytiredofnomcom/followers","following_url":"https://api.github.com/users/alreadytiredofnomcom/following{/other_user}","gists_url":"https://api.github.com/users/alreadytiredofnomcom/gists{/gist_id}","starred_url":"https://api.github.com/users/alreadytiredofnomcom/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alreadytiredofnomcom/subscriptions","organizations_url":"https://api.github.com/users/alreadytiredofnomcom/orgs","repos_url":"https://api.github.com/users/alreadytiredofnomcom/repos","events_url":"https://api.github.com/users/alreadytiredofnomcom/events{/privacy}","received_events_url":"https://api.github.com/users/alreadytiredofnomcom/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-22T12:05:39Z","updated_at":"2016-09-22T12:05:39Z","closed_at":null,"body":"Bin:\r\n“class-of-services”: should we add 1R2C and 2R3C option?\r\n\r\nQin:\r\nIf we need to add IR2C and 2R3C, I propose add policer leaf under \"service-level\" as follows:\r\n\"\r\nidentity policer {\r\ndescription\r\n\"Identity of policer type\";\r\n}\r\n\r\nidentity one-rate-two-color {\r\nbase policer;\r\ndescription\r\n\"Identity of one-rate, two-color (1R2C)\"; }\r\n\r\nidentity two-rate-three-color {\r\nbase policer;\r\ndescription\r\n\"Identity of two-rate, three-color (2R3C)\"; } Container service-level{ leaf policer { type identityref { base policer; } description \"The policer can be either one-rate, two-color (1R2C) or two-rate, three-color (2R3C)\"; } } \"\r\n\r\nAlso I am wondering if we need to change cos-identifier node type from string to identityref since cos-identifier supports EVC or EVC+CVLAN Do we also need to change color-identifier node type from string to identityref sicne color-identifier supports EVC or EVC + CVLAN?\r\n\r\n         |           |  +--rw service-level\r\n         |           |     +--rw cos-identifier?                  String (do we need to change string into identityref?)\r\n         |           |     +--rw color-identifier?                string\r\n         |           |     +--rw ingress-bw-profile-per-evc?       string\r\n         |           |     +--rw ingress-bw-profile-per-cos-id?     string\r\n         |           |     +--rw egress-bw-profile-per-evc?        string\r\n         |           |     +--rw egress-bw-profile-per-cos-id?      string\r\n         |           |     +--rw byte-offset?                    uint16\r\n         |           |     +--rw COS?                          uint32\r\n"}}
{"actor":{"display_login":"alreadytiredofnomcom"}}