Open Issues. (a) Notwithstanding any provision of the Registry Agreement to the contrary (including Sections 7.6 and 7.7 thereof), Registry Operator agrees that the following requirements, procedures and provisions of the Registry Agreement (including the documents incorporated by reference therein) may be modified and amended by ICANN after the date hereof, without the consent of Registry Operator:
i. Specification 6 – Registry Interoperability and Continuity Specifications;
ii. Trademark Clearinghouse Requirements (§ 1 of Specification 7 of the Registry Agreement);
iii. Trademark Post-‐Delegation Dispute Resolution Procedure (§ 2.a of Specification 7 of the Registry Agreement);
Open Issues. Notwithstanding any provision of the Registry Agreement to the contrary (including Sections 7.6 and 7.7 thereof), Registry Operator agrees that the following requirements, procedures and provisions of the Registry Agreement (including the documents incorporated by reference therein) may be modified and amended by ICANN after the date hereof, without the consent of Registry Operator: Specification 6 – Registry Interoperability and Continuity Specifications; Trademark Clearinghouse Requirements (§ 1 of Specification 7 of the Registry Agreement); Trademark Post-Delegation Dispute Resolution Procedure (§ 2.a of Specification 7 of the Registry Agreement); Registration Restriction Dispute Resolution Procedure (§ 2.a of Specification 7 of the Registry Agreement); Uniform Rapid Suspension (§ 2.b of Specification 7 of the Registry Agreement); Specification 11 – Public Interest Commitments (including the Public Interest Commitment Dispute Resolution Process); and any provision or term of the Registry Agreement that is the subject of advice or comment from the Governmental Advisory Committee (including any advice or comment to include new provisions in the Registry Agreement). Any such modifications and amendments are referred to herein as a “Required Change.” ICANN’s right to implement Required Changes under this Supplement shall expire on 15 January 2014. ICANN agrees that when it determines to make a Required Change, ICANN will provide Registry Operator written notice of such Required Change, which notice shall specify the terms of the Required Change (a “Change Notice”). Registry Operator agrees that, following its receipt of a Change Notice, the Required Change related thereto will be immediately effective and binding on ICANN and Registry Operator, and shall be incorporated by reference into the Registry Agreement without any action of the parties. If requested by ICANN, Registry Operator shall execute an amendment to the Registry Agreement to reflect any Required Change. Within thirty (30) calendar days of receipt of a Change Notice, Registry Operator may terminate the Registry Agreement upon five (5) calendar days written notice to ICANN; provided, however, that Registry Operator may not terminate the Registry Agreement pursuant to this Section 1(c) following the first delegation of the TLD to nameservers designated by Registry Operator into the root-zone. Upon expiration of such thirty (30) calendar day period, Registry Operator may not thereafter terminate ...
Open Issues. If a Notice of Disagreement has been received by the Buyer pursuant to paragraph 1.2 of this Schedule 3, the parties shall try to amicably resolve the issue. Should they fail to do so within twenty (20) Business Days of the end of the aforesaid objection period of forty-five (45) days (for the purpose of this Schedule the “Disagreement Date”) then any such unresolved issue (for the purpose of this Schedule the “Open Issues”) shall be submitted to and settled by an accountant of a firm of international repute and with sufficient and relevant expertise (for the purpose of this Schedule the “Accountant”) to be jointly appointed by the parties within fourteen (14) days of the Disagreement Date or, if the parties fail to agree on such appointment within that period, each party may make an application to the President of the Institute of Chartered Accountants in England and Wales to appoint the Accountant.
Open Issues. 4-21 1.4 LIST OF ILLUSTRATIONS FIGURE 2-1: FEEDER NETWORK BUILDING BLOCKS........................................2-8 FIGURE 3-1: CENTRAL STATION RELEASE 1 - REDUNDANT CONFIGURATION..................3-16 FIGURE 3-2: CENTRAL STATION RELEASE 2 - REDUNDANT CONFIGURATION..................3-17 FIGURE 3-3: CSC BLOCK DIAGRAM....................................................3-18 FIGURE 3-4: TERMINAL STATION DIGITAL CARD (SIC)..................................3-19 TABLE 2-I: AIRSTAR AND FEEDER PRODUCT TERMINOLOGY.................................2-8 TABLE 3-1: TRAFFIC TRANSPORT FUNCTIONS............................................3-9 TABLE 3-2: TRAFFIC CAPACITY OPTIONS...............................................3-9 TABLE 3-3: RADIO SPECIFICATIONS (26 GHZ).........................................3-10 TABLE 3-4: RADIO SPECIFICATIONS (10 GHZ).........................................3-12 TABLE 3-5: TERMINAL STATION......................................................3-14
Open Issues. A comprehensive and consolidated list of all outstanding problems related to the Product installation, project or other development effort that are identified by MetroPCS and Supplier as remaining to be resolved.
Open Issues. (i) Any open issues should be specified in the CR.
(ii) Any open issues should be reviewed in the CAB meeting
Open Issues. 1. Format of MFcR2 commands/status/parameters needs to be expanded to handle compelled signalling.
2. References and glossary need to be completed.
Open Issues. 1. Hot Standby Switch time of [***] ms may not be feasible. However release 2 ill incorporate switch-over mechanism with average switch time [***] ms.
2. LCT at the TS, is it needed? Probably for prototype products only.
3. Are AIS and LOS and loss of frame sufficient indications of E1/T1 switch over at the TS? Probably yes.
Open Issues. 3 (i) If one of the competing assignment contracts was made under a different legal regime, it will be to the court (→ Art. 1.11 1st hyphen) to decide on a case-by-case basis according to the law determined applicable under the applicable private international law.12 Usually there will be no tri-partite dispute resolution, so that the risk of diverging decisions exits. The possible scenarios of dispute are multiple.13
Open Issues. 4-21 1.4 LIST OF ILLUSTRATIONS FIGURE 2-1: FEEDER NETWORK BUILDING BLOCKS........................................2-8 FIGURE 3-1: CENTRAL STATION RELEASE 1 - REDUNDANT CONFIGURATION..................3-16 FIGURE 3-2: CENTRAL STATION RELEASE 2 - REDUNDANT CONFIGURATION..................3-17 FIGURE 3-3: CSC BLOCK DIAGRAM....................................................3-18 FIGURE 3-4: TERMINAL STATION DIGITAL CARD (SIC)..................................3-19 [***] CONFIDENTIAL TREATMENT REQUESTED
