Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Contact State / Province (sp) Policy #19

Closed
james-f-gould opened this issue Aug 13, 2018 · 1 comment
Closed

Contact State / Province (sp) Policy #19

james-f-gould opened this issue Aug 13, 2018 · 1 comment

Comments

@james-f-gould
Copy link
Owner

Patrick Mevzek comment on the REGEXT mailing list (https://mailarchive.ietf.org/arch/msg/regext/l1x3ods6hGkdA9fi2yOqqI9WdCc):

  • contact:sp : one registry has this rule "if the contact is in country X - the registry country - then
    the should be the 2 letters code of the nation provinces", that is not free form.

Jim Gould's reply to comment on the REGEXT mailing list:

That would be really difficult to communicate declaratively if the rule is derived from the value of a different element (e.g,. contact:cc). So, this policy only applies if the contact:cc matches the country code of the registry?

I believe this is best handled via a server-specific policy extension, since it is unique and will lead to undue complexity in defining a generic solution.

@james-f-gould
Copy link
Owner Author

Providing a specific encoding scheme for the state / province only when the contact country code matches the registry, is something very specific. My recommendation is for the registry with this unique policy to create a server-specific policy extension to formally define the list of acceptable contact:sp values based on a given country:cc value. I'm going to close this issue for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant