A. Name: Policy on the use of @upenn.edu address space
B. Number: 20081204-upenn-namespace
C. Author: M. Muth, (ISC)
[ ] proposed [ ] under review [X] approved [ ] rejected [ ] obsolete
E. Date proposed: [2007-9-19]
F. Date revised: N/A
G. Date approved: [2008-12-04]
H. Effective date: [2008-12-16]
II. Authority and Responsibility
Information Systems and Computing has custodial responsibilty and accountability for the University of Pennsylvania's email@example.com forwarding service which is integral to the operation of the Penn-wide address space for services such as email.
III. Executive Summary
This policy specifies the naming requirements for the creation/changing of new/existing names within the @upenn.edu email address space.
The purpose of this policy is to provide naming requirements and limitations that will provide a scalable solution to requests for @upenn.edu email addresses. This policy will enable the schools, departments, and university-wide computing services to have global and local name identity. While it may seem reasonable to grant the creation of any @upenn.edu email address request, a structured approach to naming conventions will provide a less ambiguous solution in reducing confusion and/or contention for Penn-wide email addresses. Additionally, the turn around time for @upenn.edu address requests will be expedited due to this process of standardization.
V. Risk of Non-compliance
If @upenn.edu addresses are not handled in compliance with this policy, email addresses will be ambiguous, potentially resulting in inconvenience to end users, misdirected email, and contention for ownership of email addresses.
This policy covers naming that falls within the @upenn.edu email address space.
VIII. Statement of policy
IX. Recommendations and Best Practices
A. Verification: Verification of this policy will occur when ISC support staff process @upenn.edu creation or change requests or during the course of troubleshooting.
B. Notification: Notification of compliance issues will be made to PennNames sponsors, domain name holders, associated LSPs and computing directors.
C. Remedy: New @upenn.edu address creation or change requests must fall within policy. Non-compliant addresses created prior to this policy should be resolved as soon as possible.
D. Financial Implications: The requesters of @upenn.edu addresses bear the costs associated with address creation and modification requests. For name assignment under Statement of Policy #1, the cost is included as part of the fee for the associated service. For all other cases, there will be a charge for one hour of consulting work at published Labor Rates (see References, below).
E. Responsibility: Responsibility for complying with this policy lies with PennName sponsors, domain name holders, and ISC.
F. Time Frame: New requests that fall within policy compliance can be granted within 3 business days, but typically 1 business day for addresses assigned under Statement of Policy #1. Expedited requests can be handled within 1 business day, at 1.5 times the standard Labor Rate (see Financial Implications and References). Requests that involve appeals to this policy can take substantially longer.
G. Enforcement: Failure to comply with policy and with the appeals process will lead to denial of an @upenn.edu address creation or change request.
H. Appeals: Appeals to this policy should be initially reviewed within the school or department, then sent to ISC Networking, where they will be reviewed internally. Disputes that cannot be settled will be forwarded to the Network Policy Committee for a recommended resolution. Requests should be in writing, and accompanied with an approval of a department head, or designee. The request should contain the details regarding how the domain is to be used as part of the requester's mission. The review process will take approximately 5 business days, depending on the type of request. The requestor will be notified in writing of the recommended resolution and the reasons. If either of the parties reject the NPC's recommendation, they should take the issue up with the heads of their respective schools or centers. The Vice President of Information Systems & Computing should be consulted if further resolution is required.