Draft 1.2
Alias初级教程十三 Draft拔模曲面
Alias初级教程十三Draft拔模曲面Draft拔模曲面1、绘制Draft拔模曲面点选曲面工具列中的Draft(拔模曲面),接着在绘图区点选曲线或面的边界,再按Go按钮生成拔模曲面。
接着可以手动调整曲面编辑器,圆形可调整曲面角度,方形可调整曲面长度。
2、Draft拔模曲面选项介绍双击曲面工具列中的Draft(拔模曲面),系统将弹出Draft拔模曲面选项对话框,如图所示Angle:拔模面与坐标平面的角度值。
在坐标X/Y/Z中先设定拔模方向。
如下图Surface Depth:拔模面的深度值Double Sided后面打勾,将产生两个方向同时拔模的面。
Multi-surface Draft面的边界法向拔模a. 点选曲面工具列的Multi-surface Draft(面的边界法向拔模),然后选取面的边界线,点Go执行法向拔模动作b. 双击曲面工具列的Multi-surface Draft(面的边界法向拔模),Angle表示拔模面与来源面的法向夹角,Le 面的两边法向拔模。
也可以通过手动调节器改变面的角度和长度。
如果想手动调节角度,须先将Control Option 模面的长度,须先将须先将Control Options选项下的Varable类型选择Length。
如下图所示Alias小技巧a. 若将Angle数值设置为负值,则为反向的角度,若将Length数值设置为负值,则为反向长度。
b. Draft拔模工具可作用于线也可作用与面的边界,而Multi-surface Draft法向拔模只能作用于面的边界c. 所有拔模工具生成的面,V方向的阶数都是1阶,U方向的阶数与线的阶数保持一致。
3.jpg(17.23 KB, 下载次数: 0)。
工作周报(模板详见附件)
工作周报(模板详见附件) 工作周报 (Draft)周报日期: [日期]项目名称: [项目名称]本周工作内容:1. [工作内容1]- [任务1.1]- [完成情况]- [存在问题/困难]- [任务1.2]- [完成情况]- [存在问题/困难]2. [工作内容2]- [任务2.1]- [完成情况]- [存在问题/困难]- [任务2.2]- [完成情况]- [存在问题/困难]3. [工作内容3]- [任务3.1]- [完成情况]- [存在问题/困难] - [任务3.2]- [完成情况]- [存在问题/困难]下周工作计划:1. [计划1]- [任务1.1]- [预计完成时间] - [存在问题/困难] - [任务1.2]- [预计完成时间] - [存在问题/困难]2. [计划2]- [任务2.1]- [预计完成时间] - [存在问题/困难] - [任务2.2]- [预计完成时间] - [存在问题/困难]3. [计划3]- [任务3.1]- [预计完成时间]- [存在问题/困难]- [任务3.2]- [预计完成时间]- [存在问题/困难]总结与反思:本周工作中,我遇到了一些困难和问题,但经过努力和团队合作,成功解决了其中的大部分。
然而,仍存在一些需要进一步改进和解决的问题。
在下周的工作中,我将着重解决这些问题,并努力完成新的任务。
附件: [相关附件,如截图或文档]备注: [补充其他需要说明的事项]详细的周报请见附件。
模联会议主席用语
1. Introduction Introduction of the Dais2. Roll Call The Chair: The Rapporteur will do the Roll Call in alphabetic order,delegates, please raise your placards and answer …present‟ when your country‟s name are called. 主席:主席助理将按字谜顺序进行点名。
请听到名字的代表举起国家牌,并回答“到” Rapporteur:Afghanistan. Afghanistan:Present。
Rapporteur: Afghanistan is Present。
… 主席助理:阿富汗。
阿富汗:到. 主席助理:阿富汗代表到。
Rapporteur: With_____countries present, this conference is in quorum, the two-thirds majority is _______,the simple majority is _______, 20% of the number is _______. Delegates who are late for the Roll Call,please send a page to the Dais to show your presence。
主席助理:本次会议共有_____个国家出席,符合大会规定。
本次会议的三分之二多数为_____,简单多数为______,20%的国家数为______,请迟到的代表向主席团传递意向条。
3。
Setting the Speakers’ List The Chair:Now we will set up a Speakers‟ List,all delegates wishing to speak please raise your placards,I‟ll call your countries‟ names randomly. China,Russian Federation… Thank you。
First Draft Report on the EDVAC
Moore School of Electrical Engineering University of Pennsylvania June 30, 1945
This is an exact copy of the original typescript draft as obtained from the University of Pennsylvania Moore School Library except that a large number of typographical errors have been corrected and the forward references that von Neumann had not filled in are provided where possible. Missing references, mainly to unwritten Sections after 15.0, are indicated by empty {}. All added material, mainly forward references, is enclosed in { }. The text and figures have been reset using TEX in order to improve readability. However, the original manuscript layout has been adhered to very closely. For a more “modern” interpretation of the von Neumann design see M. D. Godfrey and D. F. Hendry, “The Computer as von Neumann Planned It,” IEEE Annals of the History of Computing, vol. 15 no. 1, 1993.
draft用法
draft用法
"Draft" 是一个英文单词,有多种用法和含义,下面是其中的一些常见用法:
1. 起草:指起草一份文件或文章,例如:“我正在起草一份报告。
”
2. 草稿:指初步写成的文本,通常需要进一步修改和完善,例如:“我需要再看一下这份草稿。
”
3. 征兵:指征兵入伍,例如:“他在征兵中被选中了。
”
4. 草图:指初步绘制的图形或设计,例如:“他正在画一份建筑草图。
”
5. 通风:指为了保持空气流通而设置的通风口或系统,例如:“这个房间有一个通风口。
”
6. 草案:指初步制定的计划、提案或法案,例如:“政府正在制定一个新的教育草案。
”
7. 轮流:指按照顺序轮流进行某项活动或任务,例如:“我们轮流担任主席。
”
8. 拉动:指拉动某个物体或设备,例如:“他正在拉动门把手。
”
9. 草草了事:指做事匆忙、马虎或不认真,例如:“他草草了事,没有把事情做好。
”。
DRAFT OF CONTRACT 国际贸易
DRAFT OF CONTRACTArticle 11.1 The subject of the contract shall be the delivery, installation, putting into operation,after-sales service by the Supplier at 6 counties in Gansu Province within 90 days after signature of the contract by both parties and Incoterm1 applicable shall be DDP2 o f the following supplies:Supply of distant learning equipment (2 computers, one of them withre-writer, 1 laser printer, 1 digital satellite receiver with dish, IRD, IP card,1 TV, 1 VCR, 1 DVD, 1 UPS, 1 data storage device, 1 camera, all cables,software, consumables)1.2The Supplier must comply strictly with the terms of the Special Conditions and thetechnical annex.1.3The supplies which form the subject of the contract must be accompanied by theaccessories / other items necessary for using the goods over a period of 1 year, as specified in the instructions to T enderers.1.4The place of acceptance of the supplies shall be the schools in 6 counties, the timelimits for delivery shall be 30.09.2003 and the Incoterm1 applicable shall be DDP2Article 2The supplies must originate in the European Community or in the People’s Republic of China. A certificate of origin for the supplies must be provided by the Supplier atthe latest when he requests provisional acceptance of the supplies. Failure to comply with this condition may result in the cancellation of the contract.The origin of the goods must be determined according to the Community Customs Code.Article 33.1The price of the supplies shall be that shown on the budget breakdown(Annex III). The total contract price shall be XX EUR.3.2 The price referred to in Article 3.1 above shall be the sole remuneration owed bythe Contracting Authority to the Supplier under the contract. It shall be firm andnot subject to revision.3.3Payments shall be made in accordance with the General Conditions (Articles 26to 28).Article 4Throughout the period of performance of the contract and for a period of five years following completion, the Supplier shall undertake to ensure that the services of the Commission of the European Communities, the Court of Auditors of the European Communities and the authorities of the recipient countries are given access (including by any subcontractors) to all supporting documents required for carrying out the necessary checks. T o this end, he shall undertake, given notice of eight working days, to authorise access to his premises to all persons authorised to carry out these checks.Article 5The contract is made up of the following documents, in order of precedence:- this Contract agreement;- the Special Conditions, including the technical annex (Annex II: T echnical specifications - Part 1);- the Supplier's tender, including annexes (Annex II: T echnical specifications - Part2);- the Budget breakdown (Annex III);- the General Conditions (Annex I);The various documents making up the contract shall be deemed to be mutually explanatory; in case of ambiguity or divergence, they should be read in the order in which they appear above.For all matters not covered by the above provisions, the law applicable shall be Belgian law.Article 6Any written communication relating to this Contract between the Contracting Authority and/or the Project Manager, on the one hand, and the Supplier, on the other, must state the Contract title and identification number, and must be sent by post, fax, e-mail or by hand to the following addresses:Article 7This contract shall be automatically terminated, and the Supplier shall have no right to any form of compensation, if it emerges that the award or execution of the contract has given rise to unusual commercial expenses.Such unusual commercial expenses are commissions not mentioned in the main contract or not stemming from a properly concluded contract referring to the main contract, commissions not paid in return for any actual and legitimate service, commissions remitted to a tax haven, commissions paid to a recipient who is not clearly identified or commissions paid to a company which has every appearance of being a front company.Article 8The Contracting Authority may under no circumstances be held responsible for damages caused by the Supplier, subcontractors, their employees or a third party in connection with the performance of this contract.Article 99.1 The contract may be terminated as stated in Articles 35 and 36 of the GeneralConditions.9.2 If termination results from inaction or fault on the part of the Supplier, theContracting Authority shall be entitled to compensation up to a maximum of10,000.00 EUR.9.3 If termination does not result from inaction or fault on his part, the Supplier shallbe entitled to claim damages for the injury suffered up to a maximum of10,000.00 EUR, in addition to sums owed him for services already performed.Article 10The contracting parties shall make every effort to settle amicably any dispute which may arise between them. The procedures applicable are set out in the General Conditions.Article 11The delivery period shall run from the date of the signature of the contract by both parties to 90 days.Article 12The bank account of the Supplier into which payments shall be made is: ANNEXE I: GENERAL CONDITIONS FOR SUPPLY CONTRACTS FINANCED BY THE EUROPEAN COMMUNITYCONTENTSPRELIMINARY PROVISIONS 6A RTICLE 1D EFINITIONS 6A RTICLE 2L AW APPLICABLE AND LANGUAGE OF THE CONTRACT 6A RTICLE 3O RDER OF PRECEDENCE OF CONTRACT DOCUMENTS 6A RTICLE 4C OMMUNICATIONS7A RTICLE 5A SSIGNMENT7A RTICLE 6S UB-CONTRACTING7OBLIGATIONS OF THE CONTRACTING AUTHORITY 8A RTICLE 7S UPPLY OF DOCUMENTS²8A RTICLE 8A SSISTANCE WITH LOCAL REGULA TIONS9OBLIGATIONS OF THE SUPPLIER 9A RTICLE 9 G ENERAL OBLIGA TIONS9A RTICLE 10 O RIGIN10A RTICLE 11 P ERFORMANCE GUARANTEE10A RTICLE 12I NSURANCE11A RTICLE 13P ERFORMANCE PROGRAMME12A RTICLE 14S UPPLIER'S DRAWINGS12A RTICLE 15S UFFICIENCY OF TENDER PRICES13A RTICLE 16T AX AND C USTOMS ARRANGEMENTS14A RTICLE 17 P A TENTS AND LICENCES14COMMENCEMENT AND DELAYS 14A RTICLE 18 C OMMENCEMENT ORDERS14A RTICLE 19 P ERIOD OF PERFORMANCE15A RTICLE 20 E XTENSION OF PERIOD OF PERIOD OF PERFORMANCE15A RTICLE 21 D ELA YS IN PERFORMANCE16A RTICLE 22 V ARIA TIONS16A RTICLE 23 S USPENSION19MATERIALS AND WORKMANSHIP 20A RTICLE 24 Q UALITY OF SUPPLIES20A RTICLE 25 I NSPECTION AND TESTING20PAYMENTS 22A RTICLE 26 G ENERAL PROVISIONS22A RTICLE 27 P AYMENT TO THIRD PARTIES22A RTICLE 28 D ELA YED PAYMENTS23ACCEPTANCE AND MAINTENANCE 23A RTICLE 29 D ELIVERY23A RTICLE 30 V ERIFICATION OPERATIONS24A RTICLE 31 P ROVISIONAL ACCEPTANCE25A RTICLE 32 W ARRANTY OBLIGATIONS26A RTICLE 33 A FTER-SALES SERVICE27A RTICLE 34 F INAL ACCEPTANCE27BREACH OF CONTRACT AND TERMINATION 28A RTICLE 35B REACH OF CONTRACT28A RTICLE 36 T ERMINA TION BY THE C ONTRACTING A UTHORITY28A RTICLE 37 T ERMINA TION BY THE S UPPLIER30A RTICLE 38 F ORCE MAJEURE30A RTICLE 39 D ECEASE31SETTLEMENT OF DISPUTES 32A RTICLE 40 A MICABLE SETTLEMENT OF DISPUTES32A RTICLE 41 C ONCILIA TION32A RTICLE 42 A RBITRA TION32ETHICS CLAUSES 33A RTICLE 43 E THICS CLAUSES33PRELI MINARY PROVISIONSA RTICLE 1 D EFINITIONS1.1The headings and titles in these General Conditions shall not be taken as part thereof or betaken into consideration in the interpretation of the contract.1.2Where the context so permits, words importing the singular shall be deemed to include theplural and vice versa, and words importing the masculine shall be deem ed to include the feminine and vice versa.1.3Words importing persons or parties shall include firms and companies and any organisationhaving legal capacity.A RTICLE 2 L A W APPLICABLE AND LANGUAGE OF THE CONTRACT2.1The law of the contract shall be the law indicated in the Special Conditions. For all matters whichare not covered by these General Conditions, the law of the contract shall apply.2.2The language of the contract and of all communications between the Supplier and theContracting Authority or the Project Manager shall be English.A RTICLE 3 O RDER OF PRECEDENCE OF CONTRACT DOCUMENTSUnless otherwise stipulated in the contract, the order of precedence of the contract documents shall be:- the contract agreement;- the Special Conditions, including the technical annex;- the Supplier's tender, including annexes;- Budget breakdown (annex III);- the General Conditions (annex I);- [the minutes of the information meeting/site visit].The various documents making up the contract shall be deemed to be mutually explanatory; in cases of ambiguity or divergence, they should be read in the order in which they appear above.A RTICLE 4 C OMMUNICA TIONS4.1Communications between the Contracting Authority and/or the Project Manager on the onehand, and the Supplier on the other, shall be exclusively in writing.4.2If the sender requires evidence of receipt, he shall state such requirement in the communicationand shall demand such evidence of receipt whenever there is a deadline for receipt of the communication. In any event, the sender shall take all the necessary measures to ensure receipt of his communication.4.3Wherever in the contract provision is made for the giving or issue of any notice, consent,approval, certificate or decision, any such consent, approval, certificate or decision shall not unreasonably be withheld or delayed.A RTICLE 5 A SSIGNMENT5.1An assignment shall be valid only if it is a written agreement by which the Supplier transfers hiscontract or part thereof to a third party.5.2The Supplier shall not, without the prior written consent of the Contracting Authority, assign thecontract or any part thereof, or any benefit or interest thereunder, except in the following cases:5.2.1 a charge, in favour of the Supplier's bankers, of any monies due or to become dueunder the contract; or5.2.2assignment to the Supplier's insurers, of the Supplier's right to obtain relief againstother person liable in cases where the insurers have discharged the Supplier's loss orliability.5.3For the purpose of Article 5 (2), the approval of an assignment by the Contracting Authority shallnot relieve the Supplier of his obligations for the part of the contract already performed or the part not assigned.5.4If the Supplier has assigned his contract without authorisation, the Contracting Authority may,without giving formal notice thereof, apply as of right the sanctions for breach of contract provided for in Article 35.5.5Assignees must satisfy the eligibility criteria applicable for the award of the contract.A RTICLE 6S UB-CONTRACTING6.1A sub-contract shall only be valid if it is a written agreement by which the Supplier entrustsperformance of part of his contract to a third party.6.2The Supplier shall not sub-contract without the prior written authorisation of the ContractingAuthority. The elements of the contract to be sub-contracted and the identity of the sub-contractors shall be notified to the Contracting Authority. The Contracting Authority shall within 30 days of receipt of the notification, notify the Supplier of his decision, stating the reasons should he withhold such authorisation.6.3Sub-contractors must satisfy the eligibility criteria applicable for the award of the contract.6.4The Contracting Authority shall have no contractual relations with the sub-contractor.6.5The Supplier shall be responsible for the acts, defaults and negligence of his sub-contractorsand their agents or employees, as if they were the acts, defaults or negligence of the Supplie r, his agents or employees. The approval by the Contracting Authority of the sub-contracting of any part of the contract or of the sub-contractor shall not relieve the Supplier of any of his obligations under the contract.6.6If a sub-contractor has undertaken any continuing obligation extending for a period exceedingthat of the warranty period under the contract towards the Supplier in respect of the supplies provided by the contractor, the Supplier shall, at any time after the expiration of the warranty period, transfer immediately to the Contracting Authority's request and cost, the benefit of such obligation for the unexpired duration thereof.6.7If the Supplier enters into a sub-contract without approval, the Contracting Authority may,without giving formal notice thereof, apply as of right the sanctions for breach of contract provided for in Article 35.OBLIGATIONS OF THE CONTRACTING AUTHORITYA RTICLE 7S UPPLY OF DOCUMENTS7.1Within 30 days of the signature of the contract, the Project Manager shall provide to the Supplier,free of charge, a copy of the drawings prepared for the performance of the contract as well as copies of the specifications and other contract documents. The Supplier may purchase additional copies of these drawings, specifications and other documents, insofar as they are available. Upon the issue of the warranty certificate or upon on final acceptance, the Supplier shall return to the Project Manager all drawings, specifications and other contract documents.7.2Unless it is necessary for the purposes of the contract, the drawings, specifications and otherdocuments provided by the Project Manager shall not be used or communicated to a third party without the prior consent of the Project Manager.7.3The Project Manager shall have the authority to issue to the Supplier, administrative ordersincorporating such supplementary drawings and instructions as shall be necessary for the proper and adequate execution of the contract and the rectifying of any defects therein.Article 1 Assistance with local regulations8.1The Supplier may request the assistance of the Contracting Authority in obtaining copies of laws,regulations and information on local customs, orders or by-laws of the country to which the supplies are to be delivered, which may affect the Supplier in the performance of his obligations under the contract. The Contracting Authority may provide the assistance requested to the Supplier at the Supplier's cost.8.2The Supplier shall submit to the Contracting Authority in good tim e such details of the suppliesas will enable the Contracting Authority to obtain all necessary import permits or licences.8.3The Contracting Authority shall obtain all import permits or licences required for the supplies, orany part thereof, in reasonable time having regard to the time for delivery of the supplies and completion of the contract.8.4Subject to the provisions of the laws and regulations on foreign labour of the states in which thesupplies are to be delivered, the Contracting Authority shall make all efforts necessary to facilitate the procurement by the Supplier of all required visas and permits, for the personnel whose service the Supplier and the Contracting Authority consider necessary as well as residence permits for their families.OBLIGATIONS OF THE SUPPLIERA RTICLE 9 G ENERAL OBLIGA TIONS9.1The Supplier shall perform the contract with due care and diligence including, where specified,the design, manufacture, delivery to site, erecting, testing and commissioning of the supplies and carrying out any other work including the remedying of any defects in the supplies.The Supplier shall also provide all necessary equipment, superintendence, labour and facilities required for the performance of the contract.9.2The Supplier shall comply with administrative orders given by the Project Manager. Where theSupplier considers that the requirement of an administrative order goes beyond the scope of the contract, he shall, at risk of breach of contract, give notice with reasons to the Project Manager within 30 days after receipt thereof. Execution of the administrative order shall not besuspended because of this notice.9.3The Supplier shall respect and abide by all laws and regulations in force in the State of theContracting Authority and shall ensure that his personnel, their dependants and his local employees also respect and abide by all such laws and regulations. The Supplier shall indemnify the Contracting Authority against any claims and proceedings arising from any infringement by the Supplier, his employees and their dependants of such laws and regulations.9.4The Supplier shall treat all documents and information received in connection with the contractas private and confidential and shall not, save insofar as may be necessary for the purposes of the execution thereof, publish or disclose any particulars of the contract without the prior consent in writing of the Contracting Authority or the Project Manager. If any disagreement arises as to the necessity for any publication or disclosure for the purposes of the contract, the decision of the Contracting Authority shall be final.9.5If the Supplier is a joint venture or consortium of two or more persons, all such persons shall bejointly and severally bound to fulfil the terms of the contract according to the law of the State of the Contracting Authority and shall, at the request of the Contracting Authority, designate one of such persons to act as leader with authority to bind the joint venture or consortium. The composition of the joint venture or consortium shall not be altered without the prior consent of the Contracting Authority.A RTICLE 10O RIGIN10.1Except when otherwise provided for in the Special Conditions, supplies must originate in amember State of the European Union or in one of the beneficiary countries as stated in the Invitation to Tenderers. The origin of the supplies must be determined according to the rules laid down in the Community Customs Code.10.2The Supplier must certify that the goods tendered comply with this requirement, specifying therespective country of origin. The Supplier may be required to provide more detailed information in this respect.10.3The Supplier shall present an official Certificate of Origin on provisional acceptance. Fa ilure tocomply with this obligation shall lead, after formal notice, to termination of the contract.A RTICLE 11P ERFORMANCE GUARANTEE11.1The Supplier shall, within 30 days after the receipt of the notification of the award of contract,provide to the Contracting Authority a guarantee for the full and proper performance of the contract. The amount of the guarantee shall be as specified in the Special Conditions and shall not exceed 10% of the contract price including any amounts stipulated in riders to the contract.11.2The performance guarantee shall be held against payment to the Contracting Authority for anyloss resulting from the Supplier's failure to fully and properly perform his obligations under the contract.11.3The performance guarantee shall be in the format given in Annex IV and may be provided in theform of a bank guarantee, a banker's draft, a certified cheque, a bond provided by an insurance and/or bonding company, an irrevocable letter of credit. If the performance guarantee is to be provided in the form of a bank guarantee, a banker's draft, a certified cheque or a bond, it shall be issued by a bank or insurance and/or bonding company approved by the Contracting Authority.11.4The performance guarantee shall be denominated in euro, the currency in which the contract ispayable. No payments shall be made in favour of the Supplier prior the provision of the guarantee. The guarantee shall continue to remain valid until the contract has been fully and properly performed.11.5During the performance of the contract, if the natural or legal person providing the guarantee isnot able to abide by his commitments, the guarantee shall cease to be valid. The Contracting Authority shall give formal notice to the Supplier to provide a new guarantee on the same terms as the previous one. Should the Supplier fail to provide a new guarantee, the Contracting Authority may terminate the contract.11.6The Contracting Authority shall demand payment from the guarantee of all sums for which theguarantor is liable under the guarantee due to the Supplier's default under the contract, in accordance with the terms of the guarantee and up to the value thereof. The guarantor shall, without delay, pay those sums upon demand from the Contracting Authority and may not raise any objection for any reason whatsoever. Prior to making any claim under the performance guarantee, the Contracting Authority shall notify the Supplier of the default in respect of which the claim is to be made.11.7Except for such part as may be specified in the Special Conditions in respect of after-salesservice, the performance guarantee shall be released within 30 days of the issue of the final acceptance certificate..A RTICLE 12I NSURANCE12.1Without prejudice to Article XXII of the Special Conditions, it may be required to cover thecarriage of supplies by an insurance policy, the terms of which may be laid down therein. The Special Conditions may also make provisions for other types of insurance to be borne by the Supplier.12.2Notwithstanding the obligations of the Supplier to insure in accordance with Article 12 (1) theSupplier shall be solely liable and shall indemnify the Contracting Authority and the ProjectManager against any claims by third parties for damage to property or personal injuries from the execution of the contract by the Supplier, his sub-contractors and employees in connection with the contract.A RTICLE 13P ERFORMANCE PROGRAMME13.1If the Special Conditions so require, the Supplier shall submit a programme of performance ofthe contract for the approval of the Project Manager. The programme shall contain at least the following:13.1.1the order in which the Supplier proposes to execute the contract including design,manufacture, delivery to place of acceptance, installation, testing and commissioning;13.1.2the time limits within which submission and approval of the drawings are required;13.1.3 a general description of the methods which the Supplier proposes to adopt forexecuting the contract; and13.1.4such further details and information as the Project Manager may reasonably require.13.2The approval of the programme by the Project Manager shall not relieve the Supplier from anyof his obligations under the contract.13.4No material alteration to the programme shall be made without the approval of the ProjectManager. If however, the progress of the performance of the contract does not conform to the programme, the Project Manager may instruct the Supplier to revise the programme and submit the revised programme to him for approval.A RTICLE 14S UPPLIER'S DRA WINGS14.1If the Special Conditions so provide, the Supplier shall submit to the Project Manager forapproval:14.1.1such drawings, documents and/or models as may be specified in the contract withinthe time limits laid down therein or in the programme of performance;14.1.2such drawings as the Project Manager may reasonably require for the performance ofthe contract.14.2If the Project Manager fails to notify his decision of approval referred to in Article 14 (1) withinthe time limits required by the contract or the approved programme of performance, such drawings, documents, samples or models shall be deemed to be approved at the end of the time limit specified. If no time limit is specified they shall be deemed to be approved 30 days afterreceipt.14.3Approved drawings, documents, samples and models shall be signed or otherwise identified bythe Project Manager and shall not be departed from except as otherwise instructed by the Project Manager. Any Supplier's drawings, documents, samples or models which the Project Manager fails to approve, shall be forthwith modified to meet the requirements of the Project Manager and resubmitted by the Supplier for approval.14.4The Supplier shall supply additional copies of approved drawings in the form and numbersstated in the contract or in subsequent administrative orders.14.5The approval of the drawings, documents, samples or models shall not relieve the Supplier fromany of his obligations under the contract.14.6The Project Manager shall have the right at all reasonable times to inspect all contract drawings,documents, samples or models at the Supplier's premises.14.7Before provisional acceptance of the supplies, the Supplier shall supply operation andmaintenance manuals together with drawings, which shall be in such detail as will enable the Contracting Authority to operate, maintain, adjust and repair all parts of the supplies. Unless otherwise stated in the Special Conditions, the manuals and drawings shall be in the language of the contract and in such forms and numbers as stated in the contract. The supplies shall not be considered to be completed for the purpose of provisional acceptance until such manuals and drawings have been supplied to the Contracting Authority.A RTICLE 15S UFFICIENCY OF TENDER PRICES15.1Subject to any additional provisions which may be laid down in the Special Conditions, theSupplier shall be deemed to have satisfied himself before submitting his tender as to the correctness and sufficiency of the tender and to have taken account of all that is required for the full and proper performance of the contract and to have included in his rates and prices all costs related to the supplies, in particular:15.1.1the costs of transport;15.1.2the costs of handling, packing, loading, unloading, transit, delivery, unpacking,checking, insurance and other administrative costs in connection with the supplies.The packaging shall be the property of the Contracting Authority unless the SpecialConditions provide otherwise;15.1.3the cost of documents relating to the supplies where such documents are required bythe Contracting Authority;15.1.4performance and supervision of on-site assembly and/or start up of the deliveredsupplies;15.1.5furnishing of tools required for assembly and/or maintenance of the delivered supplies;15.1.7furnishing of detailed operation and maintenance manual s for each unit of thedelivered supplies, as specified in the contract;15.1.8supervision or maintenance and/or repair of the supplies, for the period of time statedin the contract, provided that this service shall not relieve the Supplier of any warrantyobligations under the contract;15.1.9training of the Contracting Authority's personnel, at the Supplier's factory and/orelsewhere as specified in the contract.15.2Since the Supplier is deemed to have determined his prices on the basis of his own calculations,operations and estimates, he shall carry out without additional charge any work which is the subject of any item whatsoever in his tender for which he neither indicates a unit price nor a firm price.A RTICLE 16 T AX AND C USTOMS ARRANGEMENTS16.1 For supplies manufactured locally, all internal fiscal charges applicable to their manufacture areexcluded.16.2 For supplies to be imported into the country of the Contracting Authority, all duties and taxesapplicable to their importation, including V A T are excluded.16.3 Whatever the origin of the supplies, the contract is exempt from stamp and registration duties.A RTICLE 17 P A TENTS AND LICENCESUnless provided for in the Special Conditions, the Supplier shall indemnify the Contracting Authority and the Project Manager against any claim resulting from the use, as specified in the contract, of patents, licences, drawings, models or brand or trade marks, except where such infringement results from compliance with the design or specifications provided by the Contracting Authority and/or the Project Manager.COMMENCEMENT AND DELAYSA RTICLE 18C OMMENCEMENT ORDERS18.1The Contracting Authority shall fix the date on which performance of the contract is to。
大连理工大学博士学位论文格式规范
4.3Contents...................................................................................................................15
摘要的主要内容为,简述全文的目的和意义、采用方法、主要研究内容和结论。
篇幅以一页为限,摘要正文后列出3-5个关键词,关键词与摘要之间空一行。
“关键词:”是关键词部分的引导,不可省略,黑体,小四。
关键词请尽量用《汉语主题词表》等词表提供的规范词。关键词之间用分号间隔,末尾不加标点。
关键词:写作规范;排版格式;博士学位论文
学校有权保留论文并向国家有关部门或机构送交论文的复印件和电子版可以将本学位论文的全部或部分内容编入有关数据库进行检索可以采用影印缩印或扫描等复制手段保存和汇编本学位论文
博士学位论文
大连理工大学博士学位论文格式规范
The Format Criterion ofDoctoral Dissertationof DUT
3.1 The Format of Picture…………………………………………………...………….5
3.1.1 The Format Example of Picture……………………………………………..5
3.1.2 The Format Description of Picture…………………………………………..5
若有不实之处,本人愿意承担相关法律责任。
SOAP_1.2规范
W3C Working Draft 9 July 2001英文版:/TR/2001/WD-soap12-20010709/英文版的最后版:/TR/soap12/英文版编辑:Martin Gudgin (DevelopMentor)Marc Hadley (Sun Microsystems)Jean-Jacques Moreau (Canon)Henrik Frystyk Nielsen (Microsoft Corp.)中文版:/pubs/misc/soap12.htm(已经不可访问)中文版编辑:柴晓路, Fennivel Chai (DealEasy)中文版贡献者:许佑骏, Arthor Xu (DealEasy)Copyright ©2001 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.AbstractSOAP 1.2为在一个松散的、分布的环境中使用XML对等地交换结构化的和类型化的信息提供了一个简单且轻量级的机制。
这是一个基于XML的协议,同时它由四部分组成: 一个作为描述在消息中的内容以及如何处理消息的信息框架的信封(envelope),一组用于表示应用定义的数据类型的编码规则(encoding rules),一个用于表示远程过程调用和返回的约定以及一个使用底层协议进行消息交换的绑定(binding)约定。
潜在地,SOAP可以与很多其他的协议绑定使用;不过,在本文档中,只定义了SOAP与HTTP已经SOAP与HTTP Extension Framework的绑定。
Status of this DocumentThis section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.This is the first W3C Working Draft of the SOAP version 1.2 specification for review by W3C members and other interested parties. It has been produced by the XML Protocol Working Group (WG), which is part of the XML Protocol Activity.The XML Protocol Protocol Working Group has, in keeping with its charter, produced a set of requirements and usage scenarios that have been published as a Working Draft. To better evaluate SOAP/1.1 against these requirements and usage scenarios, the Working Group has produced an abstract model and a glossary of terms and concepts used by the Working Group. In addition, the Working Group has produced an issues list that describes issues and concerns raised by mapping its requirements and the XMLP abstract model against the SOAP/1.1 specification as well as issues raised on the <xml-dist-app@> mailing list against SOAP/1.1.The current name for this specification is SOAP version 1.2, this first Working Draft being based on SOAP/1.1 as per the Working Group's charter (see change log in appendix D)Comments on this document should be sent to xmlp-comments@ (public archives). It is inappropriate to send discussion emails to this address.Discussion of this document takes place on the public <xml-dist-app@> mailing list (Archives) per the email communication rules in the XML Protocol Working Group Charter.This is a public W3C Working Draft. It is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". A list of all W3C technical reports can be found at/TR/.1. 引言SOAP v1.2为在一个松散的、分布的环境中使用XML对等地交换结构化的和类型化的信息提供了一个简单且轻量级的机制。
draft是什么意思用法
draft是什么意思用法draft表达的意思有很多种,那么你知道draft做动词,名词和形容词分别都有哪些意思吗?下面店铺为大家带来draft的英语意思和相关用法,欢迎大家阅读学习!draft作名词的意思汇票;草稿;选派draft作动词的意思起草;制定;征募draft作形容词的意思初步画出或(写出)的;(设计、草图、提纲或版本)正在起草中的draft的英语音标英 [drɑ:ft] 美[dræft]draft的用法:draft的用法1:draft用作动词的基本意思是“起草,草拟,画草图”,也可作“选派,抽调”“征募,征召…入伍”解。
draft的用法2:draft可接名词或代词作宾语,也可接以as短语或动词不定式充当宾语补足语的复合宾语。
draft的英语例句1. Officials have now been delegated to start work on a draft settlement.现在已经委派官员着手起草解决方案。
2. When the first draft was completed, Nichols typed it up.当初稿完成以后,尼科尔斯将它打印了出来。
3. The money was payable by a draft drawn by the home.这笔钱可凭国内承兑的汇票支付。
4. Ten days later Carmen received a bank draft for a plane ticket.10天后卡门收到了一张用于购买机票的银行汇票。
5. You pay for the car by banker's draft in the local currency.以本币银行汇票支付车款。
6. I'm supposed to have handed in a first draft of my dissertation.我本该把论文的初稿交上去了。
memoiR 1.2-4 文档说明书
Package‘memoiR’September14,2023Title R Markdown and Bookdown Templates to Publish DocumentsVersion1.2-4URL https:///EricMarcon/memoiRBugReports https:///EricMarcon/memoiR/issuesDescription Producing high-quality documents suitable for publication directly from R is made possi-ble by the R Markdown ecosystem.'memoiR'makes it easy.It provides templates to knit memoirs,articles and slideshows with helpers to publish the docu-ments on GitHub Pages and activate continuous integration.License GPL(>=3)Encoding UTF-8RoxygenNote7.2.3SystemRequirements pandocVignetteBuilder knitrImports bookdown,distill,rmarkdown,rmdformats,usethisSuggests knitr,pkgdown,testthatNeedsCompilation noAuthor Eric Marcon[aut,cre](<https:///0000-0002-5249-321X>)Maintainer Eric Marcon<****************************>Repository CRANDate/Publication2023-09-1412:20:02UTCR topics documented:build_ghworkflow (2)build_githubpages (3)build_gitignore (4)build_readme (5)Knit (6)Index812build_ghworkflow build_ghworkflow Build GitHub Action WorkflowDescriptionBuild a Y AMLfile(.gihub/workflows/memoir.yml)to knit the documents of the project to GitHub Pages.The workflow knits all R Markdownfiles according their header:all output for-mats are produced and stored into the gh-pages branch of the project.Usagebuild_ghworkflow()DetailsAll HTML outputs have the same name so the last one knitted overwrites the previous ones.Keep only one HTML format in the header of each RMarkdownfile.No DESCRIPTIONfile is necessary in the project to install packages.They must be declared in the options code chunk of each.Rmdfile(index.Rmd for the memoir template).Two secrets must have been stored in the GitHub account:•GH_PAT:a valid access token,•EMAIL:the email address to send the workflow results to.ValueThe content of the Y AMLfile as a vector of characters,invisibly.Each element is a line of thefile.Examples##Simulate the creation of a new project#Save working directoryoriginal_wd<-getwd()#Get a temporary working directorywd<-tempfile("example")#Simulate File>New File>R Markdown...>From Template>Simple Articlermarkdown::draft(wd,template="simple_article",package="memoiR",edit=FALSE)#Go to temp directorysetwd(wd)#Make it the current projectusethis::proj_set(path=".",force=TRUE)#Build GitHub Actions Workflow scriptbuild_ghworkflow()#ContentreadLines(".github/workflows/memoir.yml")##End of the example:cleanupbuild_githubpages3 #Return to the original working directory and clean upsetwd(original_wd)unlink(wd,recursive=TRUE)build_githubpages Build GitHub PagesDescriptionCopy thefiles produced by knitting to the destination folder.Usagebuild_githubpages(destination=usethis::proj_path("docs"))Argumentsdestination destination folder of the knitted documents.DetailsProducedfiles are HTML pages and their companions(css,figures,libraries)and PDF documents.The function moves them all and the README.mdfile into the destination folder.GitHub Pages allow making a website to present them:•README.md is the home page.Make it with build_readme()to have links to the HTML and PDF outputs.•knit both HTML and PDF versions to avoid dead links.•run build_githubpages()when a document is knitted to move the outputs into the docs folder.•push to GitHub and activate GitHub Pages on the main branch and the docs folder.The function is useless in book projects:the Build the Book(i.e.the bookdown::render_book() function)takes care of every step.ValueA vector with the names of thefiles and directory that were copied if they existed(some may notbe knitted),invisibly.Examples##Not run:##Simulate the creation of a new project#Save working directoryoriginal_wd<-getwd()#Get a temporary working directorywd<-tempfile("example")4build_gitignore #Simulate File>New File>R Markdown...>From Template>Simple Articlermarkdown::draft(wd,template="simple_article",package="memoiR",edit=FALSE)#Go to temp directorysetwd(wd)#Make it the current projectusethis::proj_set(path=".",force=TRUE)##Sequence of actions to build a complete project#Build.gitignorebuild_gitignore()##Activate source control,edit your files,commit#Build README,link to HTML output only in this examplebuild_readme(PDF=FALSE)#render:knit to HTML Document(interactively:click the Knit button)rmarkdown::render(input=list.files(pattern="*.Rmd"),output_format="bookdown::html_document2")#Build GitHub Pagesbuild_githubpages()#List the GitHub Pages filessetwd("docs")list.files(recursive=TRUE)##Commit and push.Outputs will be in/docs of the master branch.##End of the example:cleanup#Return to the original working directory and clean upsetwd(original_wd)unlink(wd,recursive=TRUE)##End(Not run)build_gitignore Build.gitignoreDescriptionBuild a.gitignorefile suitable for R Markdown projects.Usagebuild_gitignore()DetailsThe.gitignorefile contains the list offiles(file name patterns)that must not be controlled by git.Run this function once in each project created from a memoiR template,before activating version control.ValueThe content of the.gitignorefile as a vector of characters,invisibly.Each element is a line of the file.build_readme5Examples##Simulate the creation of a new project#Save working directoryoriginal_wd<-getwd()#Get a temporary working directorywd<-tempfile("example")#Simulate File>New File>R Markdown...>From Template>Simple Articlermarkdown::draft(wd,template="simple_article",package="memoiR",edit=FALSE)#Go to temp directorysetwd(wd)#Make it the current projectusethis::proj_set(path=".",force=TRUE)#Build.gitignore filebuild_gitignore()#ContentreadLines(".gitignore")##End of the example:cleanup#Return to the original working directory and clean upsetwd(original_wd)unlink(wd,recursive=TRUE)build_readme Build READMEDescriptionBuild a README.mdfile that will be used as index of GitHub Pages.Usagebuild_readme(PDF=TRUE)ArgumentsPDF if TRUE(by default),a link to the PDF output is added.DetailsR Markdownfiles of the project are used to get the title and abstract of the published documents.Run this function once in each project created from a memoiR template,before build_githubpages().A link to their HTML and,optionally,PDF versions is added.Metadatafields are read in the.Rmdfiles YAML header:title,abstract and URL.ValueThe content of the README.mdfile as a vector of characters,invisibly.Each element is a line of the file.6KnitExamples##Simulate the creation of a new project#Save working directoryoriginal_wd<-getwd()#Get a temporary working directorywd<-tempfile("example")#Simulate File>New File>R Markdown...>From Template>Simple Articlermarkdown::draft(wd,template="simple_article",package="memoiR",edit=FALSE)#Go to temp directorysetwd(wd)#Make it the current projectusethis::proj_set(path=".",force=TRUE)#Build README.md filebuild_readme()#ContentreadLines("README.md")##End of the example:cleanup#Return to the original working directory and clean upsetwd(original_wd)unlink(wd,recursive=TRUE)Knit KnitDescriptionCreate documents from templatesUsageknit_all(destination=usethis::proj_path("docs"),gallery="gallery")knit_template(template,output_format,destination=usethis::proj_path("docs"),gallery="gallery")Argumentsdestination name of the folder containing GitHub pages or equivalent.gallery name of the subfolder of destination to store the knitted documents.template name of the template to knit,e.g."simple_article".output_format A character vector of the output formats to convert to.Each value must be thename of a function producing an output format object,such as"bookdown::pdf_book".Knit7DetailsThese functions are used to test the templates and produce a gallery.•knit_template()produces an HTML and a PDF output of the chosen template.•knit_all()runs knit_template()on all templates of the package.The output_format argu-ment selects the way templates are rendered:•articles may be rendered in HTML by bookdown::html_document2,bookdown::gitbook,rmd-formats::downcute(and others,see the package rmdformats)and in PDF by bookdown::pdf_book.•books may be rendered in HTML by bookdown::gitbook or bookdown::bs4_book and in PDFby bookdown::pdf_book.•slides may be rendered in HTML by bookdown::slidy_presentation2,bookdown::ioslides_presentation2 and in PDF by bookdown::beamer_presentation2.These functions are mainly used for test and documentation purposes.In projects based on thetemplates,use the Knit button(articles,presentations)or the Build the Book button(memoirs)orbookdown::render_book().ValueTRUE if all documents have been knitted and copied to the gallery,invisibly.Indexbookdown::beamer_presentation2,7 bookdown::bs4_book,7bookdown::gitbook,7bookdown::html_document2,7bookdown::ioslides_presentation2,7 bookdown::pdf_book,7bookdown::render_book(),3,7bookdown::slidy_presentation2,7build_ghworkflow,2build_githubpages,3build_githubpages(),5build_gitignore,4build_readme,5build_readme(),3Knit,6knit_all(Knit),6knit_template(Knit),6rmdformats::downcute,78。
SuperSpeed_Inter-Chip_Supplement_release_draft_1_02__19May2014
Inter-Chip Supplement to the USB Revision 3.0 SpecificationRevision 1.02 DraftMay 19, 2014Revision HistoryiiUniversal Serial Bus Specification SupplementCopyright © 2014, Texas Instruments, Hewlett-Packard Company, Intel Corporation, MicrosoftCorporation, Renesas Corporation, ST-Ericsson.All rights reservedINTELLECTUAL PROPERTY DISCLAIMERTHIS SPECIFICATION IS PROVIDED TO YOU “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY, NON-INFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE. THE AUTHORS OF THIS SPECIFICATION DISCLAIM ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY PROPRIETARY RIGHTS, RELATING TO USE OR IMPLEMENTATION OF INFORMATION IN THIS SPECIFICATION. THE PROVISION OF THIS SPECIFICATION TO YOU DOES NOT PROVIDE YOU WITH ANY LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS.All product names are trademarks, registered trademarks, or servicemarks of their respective owners.iiiContributorsChoate, James Agilent Technologies, Inc.Chong, Min Jie Agilent Technologies, Inc.Fleischer-Reumann, Michael Agilent Technologies, Inc.Herz, Michael Agilent Technologies, Inc.Marik, Thomas BitifEye Digital Test Solutions GmbH Schmitt, Alexander BitifEye Digital Test Solutions GmbH Kang, Dae Woon Broadcom Corp.Kasichainula, Kishore Broadcom Corp.Ma, Kenneth Broadcom Corp.Maiti, Shoumik Broadcom Corp.Turner, Tony Broadcom Corp.Wang, Jing Broadcom Corp.Hackett, Tom CadenceNilsson, Daniel Ericsson ABOlesen, Patrik Ericsson ABBerkema, Alan Hewlett PackardSun, Gilbert Industrial Technology Research Institute Chellappan, Satheesh Intel CorporationChen, Huimin Intel CorporationDrottar, Ken Intel CorporationDunstan, Robert Intel CorporationFroelich, Dan Intel CorporationHarriman, David Intel CorporationIcking, Henrik Intel CorporationIsmail, Rahman Intel CorporationKnuutila, Kai Intel CorporationLeucht-Roth, Ulrich Intel CorporationMukker, Anoop Intel Corporation Ramakrishnan, Sivakumar Intel Corporation Ranganathan, Sridharan Intel CorporationSaunders, Brad Intel CorporationVadivelu, Karthi R Intel CorporationGalbo, Neal Lexar Media, Inc.Geldman, John Lexar Media, Inc.Hubert, Jonathan Lexar Media, Inc.Tsai, Victor Lexar Media, Inc.Chis, Flaviu MCCI CorporationKnapen, Geert MCCI CorporationYokum, Chris MCCI CorporationivAull, Randy Microsoft CorporationMalayala, Srinivasan Microsoft CorporationYou, Yang Microsoft CorporationGillet, Michel Nokia CorporationPetrie, Richard Nokia CorporationAtukula, Radha NVIDIALai, Luke NVIDIAEitam, Ohad Qualcomm, IncGruber, George Qualcomm, IncLy, Thuan Qualcomm, IncRemple, Terry Qualcomm, IncRimoni, Yoram Qualcomm, IncWietfeldt, Rick Qualcomm, IncMuto, Kiichi Renesas Electronics Corp.Roux, Steve Renesas Electronics Corp.Teng, Peter Renesas Electronics Corp.Bohm, Mark SMSCMonks, Morgan SMSCTagami, Shigenori Sony CorporationBertholom, Cedric ST-EricssonChristiansen, Morten ST-EricssonGatto, Jean-Francois ST-EricssonRadulescu, Andrei ST-EricssonNagpal, Rajkumar STMicroelectronicsB U, Chandrashekar Synopsys, Inc.Burns, Adam Synopsys, Inc.Carvalho, Mara Synopsys, Inc.Gomes, Joaquim Synopsys, Inc.Heilman, Kevin Synopsys, Inc.Kumbhani, Shaileshkumar Synopsys, Inc.Minwalla, Behram Synopsys, Inc.Mohammad, Saleem Synopsys, Inc.Saar, Hezi Synopsys, Inc.Silva, Sergio Synopsys, Inc.Wen, Zongyao Synopsys, Inc.Carlson, Brian Texas InstrumentsHarris, Will Texas InstrumentsLey, Grant Texas InstrumentsMone, Patrick Texas InstrumentsSpetla, Hattie Texas InstrumentsvTable of Contents1Introduction (10)1.1SSIC Significant Features (11)1.2SSIC and Standard SuperSpeed Comparison (11)1.3Related Documents (12)1.4Terminology (12)1.5Acronyms and Terms (12)2Adaptation of M-PHY for the Physical Layer (14)2.1M-PHY for SSIC Overview (14)2.2M-PHY MODULE Capabilities (14)2.3M-PHY Configuration Attributes (21)2.4M-PHY State Machine (22)2.5LS-MODE Support (22)3Link Layer (31)3.1Bit and Byte Ordering (31)3.2Logical Idle and FLR non-insertion (32)3.3Line Coding (33)3.4Clock Compensation (34)3.5Data Scrambling (36)3.6PowerOn Reset and Inband Reset (37)3.7Link Layer Timing Requirements (38)3.8SSIC Link Training and Status State Machine (LTSSM) (39)4Protocol Layer (51)4.1Port Capability Link Management Packet (LMP) (51)4.2Timing Parameters (51)5Device Framework (53)5.1Dynamic Attachment and Removal (53)6MPHY.TEST (55)6.1Overview (55)6.2Entering MPHY.TEST (56)6.3Loopback Testing (57)6.4Receive Burst Testing (58)6.5Tx Compliance Mode (58)6.6Analog Loopback Mode (58)6.7MPHY.TEST Block Registers (59)7Timing Diagrams Appendix (Informative) (63)7.1SS.DISABLED TO RX.DETECT (63)7.2RX.DETECT TO POLLING (64)7.3POLLING TO U0 (65)7.4U0 TO U1 (66)7.5U1 TO U0 (67)7.6U0 TO U2/U3 (68)vi7.7U2/U3 TO U0 (69)7.8USP Disconnect (70)7.9DSP Disconnect (71)viiFiguresFigure 1-1 SSIC Layers with modifications from [USB3.0] highlighted (10)Figure 1-2 Example of an implementation with a PHY Adapter Layer to a Standard SS MAC (11)Figure 2-1 RRAP Packet Types (23)Figure 3-1 Bit Ordering (31)Figure 3-2 Byte Ordering (31)Figure 3-3 Byte Ordering in a 2 LANE Configuration (32)Figure 3-4 Byte Ordering in a 4 LANE Configuration (32)Figure 3-5 Two examples of Logical Idle insertion in a 4x LANE configuration (33)Figure 3-6 Example of SKP Insertion in a 4x LANE Configuration (35)Figure 3-7 SSIC LTSSM state diagram (40)Figure 3-8 SS.Disabled state (41)Figure 3-9 Rx.Detect Sub-state Machine (42)Figure 3-10 Polling Sub-state Machine (44)Figure 3-11 U0 Sub-state Machine (47)Figure 6-1 MPHY.TEST Overview (55)Figure 6-2 Example of an MPHY.TEST Block (56)Figure 6-3 Receive BURST Test Sequence (56)viiiTablesTable 2-1 Multi-LANE Parameters (15)Table 2-2 M-TX Capability Attributes (16)Table 2-3 M-RX Capability Attributes (18)Table 2-4 TX Configuration Attributes (21)Table 2-5 RRAP Address Map (24)Table 2-6 RRAP Timing Parameters (30)Table 3-1 Mapping of SS Control Symbols (33)Table 3-2 Link Layer Timing Parameter (38)Table 4-1 Protocol Timing Parameters (51)Table 5-1 Disconnect Timing Parameters (54)Table 6-1 MPHY.TEST Block Registers (59)ix10 1 Introduction1 USB is the ubiquitous peripheral-interconnect of choice for a large number of computing and consumer2 applications. Many systems provide a comprehensive set of software drivers to support commonly3 available USB peripherals. In addition there is an existing USB ecosystem that includes USB silicon4 suppliers, design IP houses and verification and testing vendors that lowers the cost for product5 manufacturers of USB hosts and peripherals.6 These advantages have made USB attractive as a chip-to-chip interconnect within a product (without7 use of cables or connectors). This usage has been validated by the adoption of the High Speed Inter-8 Chip Supplement [HSIC] in mobile platforms. HSIC leveraged the benefits of High Speed USB while9 optimizing the link for power, cost and complexity. However the 480 Mbps bandwidth limitation of HSIC 10 poses a limitation for the next generation of applications that require higher bandwidth.11 The USB 3.0 specification adds support for transfer speeds of 5 Gbps to address the need for higher 12 bandwidth. However the USB3.0 specification as-is does not meet the requirements of embedded inter-13 chip interfaces with respect to power and EMI robustness. To address this need, this supplement 14 describes Super Speed Inter-Chip (SSIC) as an optimized inter-chip version of USB3.0.1516 Figure 1-1 SSIC Layers with modifications from [USB3.0] highlighted17 As shown in Figure 1-1, SSIC uses the MIPI M-PHY specification as the physical layer of the18 interconnect to meet the requirements of embedded inter-chip interfaces. The MIPI M-PHY [M-PHY]19C h i p t o C h i pP o r t -t o -P o r t20specification describes a serial physical layer technology with high bandwidth capabilities, which is21specifically developed for mobile applications to obtain low pin count combined with very good power22efficiency.1.1 SSIC Significant Features2324The following summarizes the key features of SSIC:25•Support for the SuperSpeed protocol only as defined in [USB 3.0]26•Optimized for power, area, cost and EMI robustness for embedded inter-chip interfaces27•Compliant with the Type-I M-PORTs from the MIPI M-PHY specification [M-PHY]•Support for x1, x2 and x4 LANE configurations.2829This supplement only focuses on peripherals that are directly attached to hosts. Support for hubs is not 30defined and may be achieved in an implementation-specific manner.1.2 SSIC and Standard SuperSpeed Comparison3132SSIC has been designed to replace a standard SuperSpeed Controller and PHY with an implementation 33that maps the SuperSpeed controller on the MIPI M-PHY. This supplement does not specify details 34of any particular implementation and it is intended that SSIC be implementable in multiple ways,35depending on what is appropriate for a particular product.36Figure 1-2 Example of an implementation with a PHY Adapter Layer to a Standard SS MAC3738Figure 1-2 shows an example of an SSIC implementation that leverages a standard SuperSpeedcontroller with minimal modifications in the link layer and above. All specifics related to SSIC including3940bridging logic between the PIPE3 interface of the controller and the Reference M-PHY MODULE11Interface (RMMI) of the M-PHY are contained in the PHY Adapter (PA). In such an implementation, it is4142necessary for the PHY Adapter to implement whatever mechanisms are needed to allow the controller to 43operate as if it were connected to a SuperSpeed link, for example by tracking the Link Training Status44State Machine (LTSSM) and providing the expected responses on the link. Other alternatives to this45example may also be designed that are compliant to this supplement.461.3 Related Documents47This is not a stand-alone document. It is a supplement to [USB 3.0]. Any aspects of USB which are not4849specifically changed by this supplement are governed by [USB 3.0].50The following referenced documents can be found on the USB-IF website :[USB 3.0] Universal Serial Bus Revision 3.0 Specification including ECNs[HSIC] High Speed Inter-Chip USB Electrical Specification including ECNs5152The following referenced documents are published by the MIPI Alliance:[M-PHY] MIPI® Alliance Specification for M-PHY SM Version 3.0[CTS] MIPI M-PHY Conformance Test Suite531.4 Terminology5455“Shall” is normative and used to indicate mandatory requirements which are to be followed strictly in56order to conform to this standard.57“Should” is normative and used to indicate a recommended option or possibility.58“May” is normative and used to indicate permitted behavior.59“Can” is informative and used to indicate behavior which is possible or may be seen60The use of “must” and “will” is deprecated for requirements and shall only be used for statements of fact.611.5 Acronyms and Terms62This section lists and defines terms and abbreviations used throughout this specification.6364Acronyms and Terms defined in [USB 3.0] and [M-PHY] are not reproduced here. Except where explicitly noted, when there is a terminology conflict between the [USB 3.0] and [M-PHY] specifications, the [USB65663.0] definition is used in this document.1267132 Adaptation of M-PHY for the Physical Layer6869This document references the MIPI M-PHY [M-PHY] specification for the definition of the physical layer.70This section includes an overview of the relevant M-PHY features, defines required M-PHY capabilitiesand describes functionality while in the [M-PHY] LS-MODE of operation.712.1 M-PHY for SSIC Overview72The following summarizes relevant M-PHY features:7374•Requirement to implement Type-I M-PHY75•Support for PWM-G1 and HS-G1/G2/G3 BURST mode operation•SSIC profile definitions to aid in inter-operability of M-PHYs in SSIC implementations7677•M-PHY SAVE states mapped appropriately to SuperSpeed link states•Compliant to M-PHY Symbol coding (8b10b) engine for spectral conditioning and clock recovery7879•Ability to operate with shared and non-shared reference clocks.802.1.1 M-PHY Architecture and the Definition of PAIRsThe architecture of the M-PHY is defined in terms of LANEs, SUB-LINKs and LINKs. The M-PHY LINK8182shall comply with the following:83•The two SUB-LINKs of an SSIC implementation shall support the same number of LANEs.84•All LANEs in the M-PHY LINK shall enter and exit HIBERN8 simultaneously.85In addition this supplement defines the concept of a PAIR.86A LANE in the downstream SUB-LINK and a counterpart LANE in the upstream SUB-LINK are together87referred to as a PAIR. A multi-LANE implementation consists of multiple PAIRs and shall have a specific 88PAIR be statically pre-determined as PAIR0. A single-LANE implementation shall consist of only one89PAIR which shall be PAIR0.2.2 M-PHY MODULE Capabilities90The M-PHY specification defines capability, configuration and status attributes for an M-TX and for an M-9192RX MODULE. Capability attributes describe the capability of M-PHY MODULEs and may varydepending on the implementation.9394To aid in the inter-operability of devices, this document defines profiles within which specific M-PHY95Capabilities are mandated.2.2.1 Profile Definitions9697Profiles are indicated by jointly specifying the speed, the multi-LANE capabilities and the rate series such 98as:99SSIC-G gr-L l where100•g= 1, 2 or 3 and indicates the specific HS-GEAR that the M-PHY LINK operates in101•r= A or B and indicates the Rate Series that the M-PHY LINK operates in102•l= 1, 2 or 4 and indicates the number of LANEs active in each SUB-LINK (See Section 2.2.2) 103All lanes in an implementation shall only operate at the HS-GEAR that corresponds to the profile that is 104supported. An implementation is permitted to support one or more profiles, however the combination of 105different profiles supported by a specific implementation are out of scope of this specification. For106example: an SSIC-G2A-L1 may or may not choose to support SSIC-G1B-L1.14An implementation of a profile shall support the corresponding speed, multi-LANE and mandated107capabilities of the M-TX and M-RX MODULEs as specified in Section 2.2.3.108Certain M-PHY MODULE configurations attributes are chosen not based on the choice of profile or the 109mandate of this document but instead are based on implementation-specific constraints. A complete list 110of such parameters is specified in Section 2.3.1112.2.2 Multi-LANE Capabilities112An implementation may choose to feature one (x1), two (x2) or four (x4) LANEs in each SUB-LINK. 113The HS-TX LANE-to-LANE skew shall be established by the receipt of a MK0 symbol at the start of a 114HS-Burst. Receivers shall accept LANE-to-LANE skew up to the allowed limit.115For multi-LANE M-PHY LINKs, Table 2-1 specifies the required timing parameters.116Table 2-1 Multi-LANE Parameters117Symbol Parameter Value CommentsT L2L_SKEW_HS_TX Permitted skew between any twoLANEs measured at the M-TX’spins 1300ps To be measured by the receiptof MK0 at the start of a HS-BURST and as defined inSection 5.1.2.4 of [M-PHY]T L2L_SKEW_HS_RX Permitted skew between any twoLANEs measured at the receiver’spins4000ps1182.2.3 M-TX and M-RX Capabilities119An implementation shall ensure that the local and remote M-PORTs are configured to the selected120profile. M-PORTs are required to support the M-TX and M-RX capabilities required in this section.121Table 2-2 and Table 2-3 define the set of capabilities that are mandated for M-TX and M-RX MODULEs 122respectively. The tables list attributes for which this supplement imposes specific requirements.123Attributes defined by [M-PHY] which are not specified by this supplement may be set to implementation-124specific values.12512612712815Inter-Chip Supplement to the USB Revision 3.0 Specification22 2.4 M-PHY State Machine146This supplement is in compliance with the State Machine for Type-I MODULEs as described in Figure 7 147for M-TX and Figure 8 for M-RX in [M-PHY] .148However the following is to be noted:149•The LINE-CFG states are not required for SSIC implementations.150•Optical Media Converters are not supported.151Details regarding the mapping of the SSIC Link Training and Status State Machine (LTSSM) on the M-152PHY Type-I state machines are provided in Section 3.8.1532.5 LS-MODE Support154The M-TX and M-RX MODULEs enter the LS-MODE of operation following events such as a power-on-155reset, a warm reset, a USP disconnect or a DSP disconnect. Section 3.8 includes further details on the 156link layer conditions for entering LS-MODE.157The only PWM-GEAR that is used in a PWM-BURST is PWM-G1. The Remote Register Access Protocol 158(RRAP) defined in Section 2.5.2 shall be implemented for data transmission in this mode.159Data transmission in a PWM-BURST shall take place in one of the following scenarios:160•In the Rx.Detect LTSSM state between a USP and a DSP or161•in the MPHY.TEST LTSSM state when the USP or DSP operates as a DUT under the control of 162external Test Equipment.163The following section details the entry conditions for PWM-BURST in the Rx.Detect state. For details on 164the entry requirements in the MPHY.TEST state please refer to Section 6.2.1652.5.1 PWM-BURST Entry in Rx.Detect166Upon entering the Rx.Detect LTSSM state and the LS-MODE sub-state as described in Section 3.8.2, a 167DSP and an USP shall:168•Disable Support for LCCs in the M-TX for all PAIRs.169•Initiate a PWM-BURST as defined in this section.170Implementation Note:As per [M-PHY] disabling support for LCC requires configuring a value of “NO = 0” to theLCC_ENABLE Configuration Attribute in the Effective Bank and subsequently asserting theTX_CfgUpdt signal of the M-TX for all PAIRs.171The DSP shall initiate a PWM-BURST as per [M-PHY] on the M-TX MODULE of PAIR0. The DSP shall 172then monitor the M-RX of PAIR0 for the USP to initiate a PWM-BURST.173The USP shall initiate a PWM-BURST as per [M-PHY] on the M-TX MODULE of PAIR0 after it detects a 174PWM-BURST on the M-RX of PAIR0.175In a multi-LANE M-PHY LINK the remaining M-TX MODULEs shall remain in the SLEEP state.176Inter-Chip Supplement to the USB Revision 3.0 Specification232.5.2Remote Register Access Protocol (RRAP)177 While in the PWM-BURST mode, communication is achieved using the RRAP which consists of the 178 following packet types: 179 • Write Command 180 • Write Response 181 • Read Command 182 •Read Response183 An RRAP Master shall be capable of issuing Command packets while a RRAP Target shall issue 184 response packets. 185186187 Figure 2-1 RRAP Packet Types188 The RRAP packets are described in Figure 2-1 along with the following additional requirements: 189 • “LowerAddr” and “UpperAddr” values are set based on the address map defined in Table 2-5. 190 • The “Rsvd” fields shall not be used and shall be set to 0.191 • The “P” field functions as an odd-parity bit for the entire packet.192 •The entire packet is transmitted continuously without intervening symbols.193 The following requirements apply to the RRAP: 194 • When in PWM-BURST mode and not transmitting a RRAP packet, the M-TX MODULEs in SUB-195 LINKs shall transmit the FLR symbol as per [M-PHY] .196 • The RRAP follows the bit and byte ordering rules defined in Section 3.1. 197 •A DSP shall support RRAP Master functionality.198Bit ByteWrite CommandBit ByteWrite ResponseBit ByteRead CommandBitByteRead ResponseInter-Chip Supplement to the USB Revision 3.0 Specification24 •When in PWM-BURST, a DSP that supports the optional MPHY.TEST state shall support the receipt199of a Write Command to enable a transition to that state. All RRAP commands received by a DSP in 200the MPHY.TEST state shall be processed per RRAP Target functionality.201• A USP shall only support RRAP Target functionality.202•Test Equipment shall function as a RRAP Master with either the DSP or the USP as the Device203Under Test (DUT).204• A DSP serving as a RRAP Master shall only send commands and receive responses on PAIR0.205• A DSP or an USP serving as a RRAP Target shall support receiving commands over any PAIRx and 206shall return a response on the same PAIRx.207•Test Equipment serving as a RRAP Master may send commands and receive responses on any208PAIR.209•Upon receiving a Write Command packet, a Target shall transmit the corresponding response210packet within tRRAPTargetResponse. This requirement shall apply for any Write Command received 211including Writes to Reserved Registers and Registers that are identified in Table 2-5 as having no 212effect.213•Upon receiving a Read Command packet, a Target shall transmit the corresponding response214packet within tRRAPTargetResponse.215•If a Master has issued a Command, then the Master shall not retry the Command or issue another 216Command until either the Target has provided a Response, or after tRRAPInitiatorResponse has217elapsed.218• A Target shall map the attributes of all implemented PAIRs to RRAP addresses as defined in Table 2192-5.220• A Target shall not send a response until the RRAP Command is fully received with a valid parity.221Implementation Note:Additional steps to improve the reliability offered by a single parity bit may be taken at the RRAPlevel using implementation specific means such as redundant write commands or performing readsafter writes to ensure the correctness of operations.222Table 2-5 RRAP Address Map223UpperAddr LowerAddr Register Name Description0x0 0x00-0xFF As defined in [M-PHY] Capability, configuration and status attributes forPAIR0. Writes to these registers shall only affectthe shadow bank until an RCT is executed. TheTarget shall provide a Write Response only afterthe corresponding Register Write specified in theRRAP Command is committed to the shadowbank.0x1 0x00-0xFF As defined in [M-PHY] Capability, configuration and status attributes forPAIR1. Writes to these registers shall only affectthe shadow bank until an RCT is executed. TheTarget shall provide a Write Response only afterthe corresponding Register Write specified in theRRAP Command is committed to the shadowbank.Inter-Chip Supplement to the USB Revision 3.0 SpecificationUpperAddr LowerAddr Register Name Description0x2 0x00-0xFF As defined in [M-PHY] Capability, configuration and status attributes forPAIR2. Writes to these registers shall only affectthe shadow bank until an RCT is executed. TheTarget shall provide a Write Response only afterthe corresponding Register Write specified in theRRAP Command is committed to the shadowbank.0x3 0x00-0xFF As defined in [M-PHY] Capability, configuration and status attributes forPAIR3. Writes to these registers shall only affectthe shadow bank until an RCT is executed. TheTarget shall provide a Write Response only afterthe corresponding Register Write specified in theRRAP Command is committed to the shadowbank.0x4 0x00 DSP_DISCONNECT This Register is used by a DSP following a LINE-RESET to signal a DSP Disconnect. This bit isrequired only for an USP only. A DSP or a USP inthe MPHY.TEST state shall ignore writes to thisregister.Read/Write Attributes:•R/WReset Default:•0x00Bit [0]:•Writing 1’b1 signals a DSP disconnect asdetailed in Section 5.1.2.•Writing 1’b0 shall have no effect.Once the bit is set, it shall only be reset via aLINE-RESET issued either by a DSP (as part ofWarm Reset) or by Test Equipment.Bit [7:1] Reserved.•Writes shall be ignored and Reads shallreturn zero values.0x4 0x01 CONFIGURE_FOR_HS This Register is used to direct the Target toupdate its shadow bank for HS-BURST with thesettings that correspond to the SSIC profilesupported. As noted in Section 2.2.1 this profile isstatically determined and this supplementprovides no means for selecting between differentprofiles if so supported. The Target shall provide aWrite Response only after the correspondingRegister Write specified in the RRAP Command iscommitted to the shadow bank.25Inter-Chip Supplement to the USB Revision 3.0 SpecificationUpperAddr LowerAddr Register Name DescriptionA Master may alternatively choose to not use thisregister in which case it shall rely on a set ofimplementation-specific RRAP commands toupdate the shadow bank of the Target for HS-BURST operation.Read/Write Attributes:•R/WReset Default:•0x00Bit [0]:•Writing 1’b1 directs the Target to updateits shadow bank with the settings thatcorrespond to its SSIC profile.•Writing 1’b0 shall have no effect.Once the bit is set, it shall only be reset via aLINE-RESET issued either by a DSP (as part ofWarm Reset) or by Test Equipment.Bit[7:1] Reserved.•Writes shall be ignored and Reads shallreturn zero values.0x4 0x02 BURST_CLOSURE This Register is used to direct the Target toterminate the PWM-BURST.Read/Write Attributes:•R/WReset Default:•0x00Bit [0]:•Writing 1’b1 terminates the PWM-BURSTand initiates an RCT to exit LS-MODE asdefined in Section 2.5.3.•Writing 1’b0 shall have no effect.Once the bit is set, it shall only be reset via aLINE-RESET issued either by a DSP (as part ofWarm Reset) or by Test Equipment.Bit[7:1] Reserved.•Writes shall be ignored and Reads shallreturn zero values.0x4 0x03 DISABLE_SCRAMBLING This Register is used by a DSP to indicate to anUSP that data transmission in HS-MODE shall 26Inter-Chip Supplement to the USB Revision 3.0 SpecificationUpperAddr LowerAddr Register Name Descriptionhave scrambling disabled.Read/Write Attributes:•R/WReset Default:•0x00Bit [0]:•Writing 1’b1 configures the USP todisable HS-MODE scrambling.•Writing 1’b0 shall have no effect.Once the bit is set, it shall only be reset via aLINE-RESET issued either by a DSP (as part ofWarm Reset) or by Test Equipment.Bit [7:1] Reserved.•Writes shall be ignored and Reads shallreturn zero values.0x4 0x04 DISABLE_STALL_IN_U0 This Register is used by a DSP to disable STALLentry in U0 in an USP. A DSP or a USP in theMPHY.TEST state shall ignore writes to thisregister.Read/Write Attributes:•R/WReset Default:•0x00Bit [0]:•Writing 1’b1 configures the USP todisable STALL entry while in U0.•Writing 1’b0 shall have no effect.Once the bit is set, it shall only be reset via aLINE-RESET issued either by a DSP (as part ofWarm Reset) or by Test Equipment.Bit [7:1] Reserved.•Writes shall be ignored and Reads shallreturn zero values.0x4 0x05 DISABLE_LUP_LDN This optional Register is used by a DSP to disablethe use of the LDN and LUP Link Commandsdefined in [USB 3.0] to allow additional poweroptimizations in the M-TX.Read/Write Attributes:•R/WReset Default:27。
模拟联合国大会流程-详细介绍模联MUN的规则-议题
1、MUN模拟联合国大会简介模拟联合国(Model United Nations)是一项从美国哈佛大学起源的学生活动,活动中由学生代表们模拟各国外交官以及联合国各机构或者国际组织的议事流程来商讨解决一些热点的国际问题。
活动中,学生们模拟联合国会议中动议、辩论、磋商、写作文件、投票等流程,把握自己所代表国家的立场,维护本国的国家利益。
该活动近几年在中国兴起,从北京辐射到全国各地、从大学辐射到各地高中。
2、如何参加MUN模拟联合国大会各大学、高中的MUN组织通常是以社团的形式存在的,有的学校会以“协会”称。
在没有会议时,通常社团中的前辈会以“校内会议”的形式对新成员进行培训,并作一定程度上的选拔,为今后的会议和社团的将来发展做一定力量上的储备。
模拟联合国会议的规模大小不一,有校内会议、校际会议、全市范围的会议、全国范围的会议(如复旦大学组织的fduimun、北京大学组织的pkunmun)、乃至世界范围的会议(如蔚蓝国际wemun、美国联合国协会的UNA-USA MUN),有些组委会接受个人代表的报名,有些只接受以学校为组织的团体报名。
一般一次会议的准备周期会很长,报名后有的组委会需要各校以竞投的方式来竞投自己所代表的国家,这也是一个技术型的环节,国家的好坏将直接影响到代表在会议中的表现。
也有部分组委会没有这个环节,国家是由组委会内部分配的。
确定国家和议题之后代表就要进行会前准备,除了全面了解议题、了解自己国家的情况、确定自己的立场,完成立场文件等意外有必要的还可以和一些有结盟可能的国家代表进行会前的联系和沟通。
3、模拟联合国流程模拟联合国大会会议的流程在最大限度上模仿了联合国会议的办事流程。
下面是一份一般会议的基本流程案例:引用:1有组织核心磋商,代表须在动议中包含以下内容,即:想讨论的内容(topic)、磋商的总时间(totoal time)、每位代表的发言时间(individual time)。
PE绩效管理条例(Draft)
PE绩效管理条例(Draft)一.目的:建立** PE部门工作规定,规范人员绩效考核方式,以体现考核的科学,公平,合理,以期构建严谨,和谐,积极,活力向上的工作氛围;二.范围及标准:凡**** PE部门工作人员皆属之;满分100分/A+:优>90分 A:佳85~90 M:良好75~85 B:75分以下有待改善;三.内容:3.1本职工作(60分):3.1.1产品承接及维护:3.1.1.1所负责之产品技转顺利准时,量产后品质稳定,无重大客诉:+5~10分3.1.1.2所负责产品出现异常,品质不稳定,客诉较多,视具体情形做扣分,文件类异常每次-1~5分,工法类异常每次-1~5分,量产后出现重大设计不良-5~15分;3.1.2异常处理:3.1.2.1及时处理异常不致工时材料浪费者:+1~5分3.1.2.2未能及时处理异常而造成工时材料浪费每次-1~5分;同类异常重复发生者每次-3~5分;3.1.3制程改善3.1.3.1工作中能积极提出议案并实施有成效者:+1~10分,成效显著者视具体事迹并呈报奖励;3.1.3.2无制程改善提案者及提案无法应因实际或实施无效者:-1~3分3.2.4 KPI达成/专案管理3.2.4.1能拟订部门或小组KPI并实施有效者:+5~10分3.2.4.2未及时完成部门及小组KPI或专案管理未达标者:-1~10分3.2公司规章制度/考勤/6S(20分)3.2.1严格遵守公司各项规章制度无违规者+10分,违反者视情节程度-1~10分,特别严重者视具体行为并送挞惩处;3.2.2半年度/全年度出勤正常:+2.5/5分;3.2.3 6S:违反6S规定者每次-0.5~2.5分,半年度/全年度无违反者+2.5/5分3.3其他(20分)3.3.1技术特长并有助于其本职工作,协助同事者+1~5分;3.3.2 同仁间沟通良好,无争吵顶撞者:+1~5分,违者视情节-1~5分;3.3.3积极教导新人,积极开展教育训练者:+1~5分;3.3.4 积极参加公司各项活动者:+1~5分;。
DRAFT NIST Special Publication 800-38B DRAFT Recommendation for Block Cipher Modes of Opera
NIST Special Publication 800-38BDRAFTRecommendation for Block Cipher Modes of Operation: The RMAC Authentication ModeMethods and TechniquesMorris DworkinNovember 4, 2002AbstractThis Recommendation defines an authentication mode of operation, called RMAC, for a symmetric key block cipher algorithm. RMAC can provide cryptographic protection of sensitive, but unclassified, computer data. In particular, RMAC can provide assurance of the authenticity and, therefore, of the integrity of the data.KEY WORDS: Authentication; block cipher; cryptography; encryption; Federal Information Processing Standard; information security; integrity; mode of operation.Table of Contents1PURPOSE (5)2AUTHORITY (5)3INTRODUCTION (5)4DEFINITIONS, ABBREVIATIONS, AND SYMBOLS (6)4.1D EFINITIONS AND A BBREVIATIONS (6)4.2S YMBOLS (7)4.2.1Variables (7)4.2.2Operations and Functions (8)5PRELIMINARIES (9)5.1T HE U NDERLYING B LOCK C IPHER A LGORITHM (9)5.2E LEMENTS OF RMAC (9)5.3E XAMPLES OF O PERATIONS AND F UNCTIONS (10)6RMAC SPECIFICATION (10)6.1M ESSAGE F ORMATTING (10)6.2P ARAMETER S ETS (10)6.3MAC G ENERATION (11)6.4T AG G ENERATION AND V ERIFICATION (12)APPENDIX A: SECURITY CONSIDERATIONS (13)A.1E XHAUSTIVE K EY S EARCH (13)A.2G ENERAL F ORGERY (13)A.3E XTENSION F ORGERY B ASED ON A C OLLISION (13)A.4S UMMARY OF S ECURITY P ROPERTIES OF P ARAMETER S ETS (14)APPENDIX B: THE GENERATION OF RMAC PARAMETERS (15)B.1 D ERIVATION OF RMAC KEYS FROM A M ASTER K EY (15)B.2 S ALT G ENERATION (15)APPENDIX C: EXAMPLE VECTORS FOR THE MAC GENERATION FUNCTION (16)C.1RMAC-AES128 E XAMPLE V ECTORS (16)C.1.1RMAC-AES128-I (16)C.1.2RMAC-AES128-II (17)C.1.3RMAC-AES128-III (18)C.1.4RMAC-AES128-IV (19)C.1.5RMAC-AES128-V (20)C.2RMAC-AES192 E XAMPLE V ECTORS (21)C.2.1RMAC-AES192-I (21)C.2.2RMAC-AES192-II (22)C.2.3RMAC-AES192-III (23)C.2.4RMAC-AES192-IV (24)C.2.5RMAC-AES192-V (26)C.3RMAC-AES256 E XAMPLE V ECTORS (27)C.3.1RMAC-AES256-I (27)C.3.2RMAC-AES256-II (28)C.3.3RMAC-AES256-III (29)C.3.4RMAC-AES256-IV (30)C.3.5RMAC-AES256-V (32)C.4RMAC-TDES112 E XAMPLE V ECTORS (33)C.5RMAC-TDES168 E XAMPLE V ECTORS (33)APPENDIX D: REFERENCES (34)Table of FiguresFigure 1: The RMAC MAC Generation Function (12)1 PurposeThis publication is the second part in a series of Recommendations regarding modes of operation of symmetric key block cipher algorithms.2 AuthorityThis document has been developed by the National Institute of Standards and Technology (NIST) in furtherance of its statutory responsibilities under the Computer Security Act of 1987 (Public Law 100-235) and the Information Technology Management Reform Act of 1996, specifically 15 U.S.C. 278 g-3(a)(5). This is not a guideline within the meaning of 15 U.S.C. 278 g-3 (a)(5).This Recommendation is neither a standard nor a guideline, and as such, is neither mandatory nor binding on federal agencies. Federal agencies and nongovernment organizations may use this Recommendation on a voluntary basis. It is not subject to copyright.Nothing in this Recommendation should be taken to contradict standards and guidelines that have been made mandatory and binding upon federal agencies by the Secretary of Commerce under statutory authority. Nor should this Recommendation be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, the Director of the Office of Management and Budget, or any other federal official.Conformance testing for implementations of the modes of operation that are specified in this Recommendation will be conducted within the framework of the Cryptographic Module Validation Program (CMVP), a joint effort of NIST and the Communications Security Establishment of the Government of Canada. An implementation of a mode of operation must adhere to the requirements in this Recommendation in order to be validated under the CMVP. The requirements of this Recommendation are indicated by the word “shall.”3 IntroductionThis Recommendation specifies an algorithm, RMAC [1], that can provide assurance of data origin authentication and, hence, assurance of data integrity. In particular, RMAC is an algorithm for generating a message authentication code (MAC) from the data to be authenticated and from an associated value called the salt, using a block cipher and two secret keys that the parties to the authentication of the data establish beforehand. One party generates the MAC and provides the MAC and the associated salt as the authentication tag; subsequently, any party with access to the secret keys may verify whether the received MAC was generated from the received data and the received salt. Successful verification of the MAC provides assurance of the authenticity of the data, i.e., that it originated from a source with access to the secret keys. Consequently, successful verification of the MAC also provides assurance of the integrity of the data, i.e., that it was not altered after the generation of the MAC.A MAC is sometimes called a cryptographic checksum, because it is generated from a keyed cryptographic algorithm in order to provide stronger assurance of data integrity than an ordinary checksum. The verification of an ordinary checksum or an error detecting code is designed to reveal only accidental modifications of the data, while the verification of a MAC is designed to reveal intentional, unauthorized modifications of the data, as well as accidental modifications. Because RMAC is constructed from a block cipher algorithm, RMAC can be considered a mode of operation of the block cipher algorithm. The block cipher algorithm shall be approved, i.e., specified or adopted in a Federal Information Processing Standard (FIPS) or a NIST Recommendation; for example, FIPS Pub. 197 [2] specifies the AES algorithm, and FIPS Pub. 46-3 [3] adopts the Triple DES algorithm.FIPS Pub. 198 [4] specifies a different MAC algorithm, called HMAC, that is also appropriate for the protection of sensitive data. Because HMAC is constructed from a hash function rather than a block cipher algorithm, RMAC may be preferable for application environments in which an approved block cipher is more convenient to implement than an approved hash function.4 Definitions, Abbreviations, and Symbols4.1 Definitions and AbbreviationsApproved FIPS approved or NIST recommended: an algorithm or technique thatis either 1) specified in a FIPS or NIST Recommendation, or 2) adoptedin a FIPS or NIST Recommendation.Authenticity The property that data indeed originated from its purported source. Authentication Mode A block cipher mode of operation that can provide assurance of theauthenticity and, therefore, the integrity of data.Authentication Tag (Tag) A pair of bit strings associated to data to provide assurance of its authenticity: the salt and the message authentication code that is derived from the data and the salt.Bit A binary digit: 0 or 1.Bit String An ordered sequence of 0s and 1s.Block A bit string whose bit length is the block size of the block cipheralgorithm.Block Cipher See forward cipher function.Block Cipher Algorithm A family of functions and their inverses that is parameterized by cryptographic keys; the functions map bit strings of a fixed length to bit strings of the same length.Block Size The number of bits in an input (or output) block of the block cipher. Cryptographic Key A parameter used in the block cipher algorithm that determines theforward cipher function.Data Integrity The property that data has not been altered by an unauthorized entity. Exclusive-OR The bitwise addition, modulo 2, of two bit strings of equal length. FIPS FederalInformationProcessing Standard.Forward Cipher Function One of the two functions of the block cipher algorithm that is determined by the choice of a cryptographic key.Initialization Vector(IV)A data block that some modes of operation require as an initial input.Message Authentication Code (MAC) A cryptographic checksum on data that is designed to reveal both accidental errors and intentional modifications of the data.Mode of Operation (Mode) An algorithm for the cryptographic transformation of data that features a symmetric key block cipher algorithm.Most Significant Bit(s) The left-most bit(s) of a bit string.Nonce A value that is used only once within a specified context.RMAC The name of the authentication mode that is specified in thisRecommendation.Salt A parameter of an algorithm whose role is to randomize the value ofanother parameter.4.2 Symbols4.2.1 Variablesb The block size, in bits.k The key length for the block cipher.m The bit length of the RMAC MAC.n The number of data blocks in the padded message.r The bit length of the salt.CNST j The j th fixed, i.e., constant, block.K A block cipher key.K1 The first RMAC key.K2 The second RMAC key.K3 A key that is derived from the second RMAC key and the salt.M The message.Mlen The bit length of the message.M j The j th block in the partition of the padded message.j th output block.O j ThePAD The padding that is appended to the message.salt.R The4.2.2 Operations and Functions0s The bit string consisting of s ‘0’ bits.X || Y The concatenation of two bit strings X and Y.X ⊕Y The bitwise exclusive-OR of two bit strings X and Y of the same length.CIPH K(X) The forward cipher function of the block cipher algorithm under the key K applied to the data block X.MSB s(X) The bit string consisting of the s most significant bits of the bit string X.RMAC(R,M) The RMAC message authentication code for message M with salt R.5 Preliminaries5.1 The Underlying Block Cipher AlgorithmThe RMAC algorithm specified in this Recommendation depends on the choice of an underlying symmetric key block cipher algorithm; the RMAC algorithm is thus a mode of operation (mode, for short) of the symmetric key block cipher. The underlying block cipher algorithm must be approved, and two secret, random keys for the block cipher algorithm shall be established. The keys regulate the functioning of the block cipher algorithm and, thus, by extension, the functioning of the mode. The specifications of the block cipher algorithm and the mode are public, so the security of the mode depends, at a minimum, on the secrecy of the keys.For any given key, the underlying block cipher algorithm of the mode consists of two processes that are inverses of each other. As part of the choice of the block cipher algorithm, one of the two processes of the block cipher algorithm is designated as the forward cipher function. The inverse of this process is called the inverse cipher function. Because the RMAC mode does not require the inverse cipher function, the forward cipher function in this Part of the Recommendation is simply called the block cipher.5.2 Elements of RMACThe block cipher keys that are required for the RMAC mode are bit strings, denoted K1and K2, whose bit length, denoted k, depends on the choice of the block cipher algorithm. The keys shall be random or pseudorandom, distinct from keys that are used for other purposes, and secret. The two keys shall each be established by an approved key establishment method, or the keys shall be derived from a single key K, which is established by an approved key establishment method.A method for deriving K1and K2 from a single, master key K is given in Appendix B.1.The block cipher is a function on bit strings of a fixed bit length. The fixed bit length of the bit strings is called the block size and is denoted b; any bit string whose bit length is b is called a (data) block. Under a key K, the block cipher function is denoted CIPH K.For the AES algorithm, b=128 and k=128, 192, or 256; for Triple DES, b=64 and k=112 or 168. The data to be authenticated is one input to the RMAC MAC generation function; the data in this context is called the message, denoted M.Another input to the MAC generation function is a parameter associated with the message called the salt, denoted R. The role of the salt in the MAC generation function is to randomize (i.e., “flavor”) the second key, K2. The bit length of the salt, denoted r, is determined by the choice of a parameter set that is specified in Section 6.2. The use of the salt is optional in the sense that a parameter set may be chosen in which r=0. When r1234567487569 4 9 4 7 7 5 45674 54 6 4 ensure that the expected probability of repeating the salt for different messages is negligible. The generation of the salt is discussed further in Appendix B.2.The RMAC MAC generation function is denoted RMAC, so that the output of the function, the MAC, is denoted RMAC(R,M). The bit length of the MAC, denoted m, is determined by thechoice of a parameter set that is specified in Section 6.2. The authentication tag to the message is the ordered pair (R, RMAC(R,M)); thus, the tag consists of one part, the salt, that may be independent of the message and a second part, the MAC, that depends on both the salt and the message. The total number of bits in the tag is r+m.5.3 Examples of Operations and FunctionsFor a nonnegative integer s, the bit string consisting of s ‘0’ bits is denoted 0s.The concatenation operation on bit strings is denoted ||; for example, 001 || 10111 = 00110111.Given bit strings of equal length, the exclusive-OR operation, denoted ⊕, specifies the addition, modulo 2, of the bits in each bit position, i.e., without carries. Thus, 10011 ⊕ 10101= 00110, for example.The function MSB s returns the s most significant bits of the argument. Thus, for example, MSB4(111011010) = 1110.6 RMAC Specification6.1 Message FormattingThe first steps of the MAC generation function are to append padding to the message and to partition the resulting string into complete blocks. The padding, denoted PAD, is a single ‘1’ bit followed by the minimum number of ‘0’ bits such that the total number of bits in the padded message is a multiple of the block size. The padded message is then partitioned into a sequence of n complete blocks, denoted M1, M2, …, M n. Thus,M || PAD = M1 || M2 ||…|| M n .If the bit length of M is a multiple of the block size, then PAD = 1 || 0b-1, i.e., a complete block.6.2 Parameter SetsA parameter set is a pair of values for the bit lengths r and m of the two parts of the authentication tag, the salt and the MAC. The parameter sets for RMAC depend on the block size of the underlying block cipher algorithm. A parameter set shall be chosen from Table 1 below; five parameter sets are given for the 128 bit block size, and two for the 64 bit block size. Although parameter set I offers the shortest authentication tags, it is not recommended for general use. The decision to use parameter set I requires a risk-benefit analysis of at least three factors: 1) the relevant attack models, 2) the application environment, and 3) the value and longevity of the data to be protected. In particular, parameter set I shall only be used if the controlling protocol or application environment sufficiently restricts the number of times that verification of an authentication tag can fail under any given pair of RMAC keys. For example,the short duration of a session, or, more generally, the low bandwidth of the communication channel may preclude many repeated trials.Parameter sets II, III, IV, and V are appropriate for general use.Table 1: Parameter Setsb=128 b=64Parameter Set r m r m32I 03264 6464II 0n/a80III 16n/a96IV 64V 128 128 n/aSome of the security considerations that underlie the selection of a parameter set are summarized in Appendix A. The expected work factors for important aspects of the attacks that are discussed in the appendix are summarized for each parameter set in Table 2 in Section A.4.6.3 MAC GenerationThe following is a specification of the RMAC MAC generation function:Input:block cipher CIPH;block cipher keys K1 and K2 of bit length k;parameter set (r, m);message M;salt R of bit length r.Output:message authentication code RMAC(R, M) of bit length m.Steps:toM the padding string PAD, as described in Section 6.1.1. Append2.Partition M || PAD into n blocks M1, M2, …, M n, as described in Section 6.1.3.O1 =CIPH K1(M1).j = 2 to n, do O j= CIPH K1(M j⊕O j-1).4. Forr=0, then K3=K2; else K3 = K2 ⊕ (R || 0k-r).5. If6.Return RMAC(R, M) = MSB m(CIPH K3(O n)).The calculations in Steps 3 and 4 are equivalent to encrypting the padded message using the cipher block chaining (CBC) mode [5] of the block cipher, under the first RMAC key, with the zero block as the initialization vector. However, unlike CBC encryption, in which every output block from Steps 3 and 4 is part of the encryption output (i.e., the ciphertext), in RMAC, the output blocks in Steps 3 and 4 are intermediate results. In Step 6, the block cipher under a newkey is applied to the final output block from Step 4, and the result is truncated as specified in the parameter set. The new key for this final application of the block cipher is obtained in Step 5 by exclusive-ORing the salt into the most significant bits of the second RMAC key.The RMAC MAC generation function is illustrated in Figure 1.6.4 Tag Generation and VerificationThe prerequisites for the authentication process are the establishment of an approved block cipher algorithm, two secret RMAC keys, and a parameter set1 among the parties to the authentication of the data.To generate an authentication tag on a message M, a party shall determine an associated salt R in accordance with Appendix B, generate RMAC(R,M), as specified in Section 6.3, and provide the authentication tag (R, RMAC(R,M)) to the data.To verify an authentication tag (R', MAC'), a party shall apply the RMAC MAC generation function, as specified in Section 6.3, to the received message M' and the received salt R' within the tag. If the computed MAC, i.e., RMAC(R',M'), is identical to the received MAC, i.e., MAC', then verification succeeds; otherwise, verification fails, and the message should not be considered authentic.1 For tag verification, the parameter set is implicit in the bit length of the tag.Appendix A: Security ConsiderationsThe submitters of RMAC present a security analysis of RMAC in [6]. In this appendix, three types of attacks on general MAC algorithms are summarized, and discussed with respect to RMAC: exhaustive key search, general forgery, and extension forgery based on birthday collisions.A.1 Exhaustive Key SearchIn principle, given sufficiently many valid message-tag pairs, an unauthorized party can exhaustively search, off-line, every possible key to the MAC generation algorithm. After recovering the secret key, by this method or any other method, the unauthorized party could generate a forgery, i.e., a valid authentication tag, for any message.The number of RMAC keys is so large that exhaustive key search of RMAC is impractical for the foreseeable future. In particular, for the key size k, which is at least 112 bits for the approved block cipher algorithms, the exhaustive search for the two RMAC keys would be expected to require the generation of 22k-1 MACs. Even if the two RMAC keys are derived from a single master key, as discussed in Appendix B.1, the exhaustive search for the master key would be expected to require the generation of 2k-1 MACs.ForgeryA.2 GeneralThe successful verification of a MAC does not guarantee that the associated message is authentic: there is a small chance that an unauthorized party can guess a valid MAC of an arbitrary (i.e., inauthentic) message. Moreover, if many message forgeries are presented for verification, the probability increases that, eventually, verification will succeed for one of them. This limitation is inherent in any MAC algorithm.The protection that the RMAC algorithm provides against such forgeries is determined by the bit length of MAC, m, which in turn is determined by the choice of a parameter set. The probability of successful verification of an arbitrary MAC with any given salt on any given message is expected to be 2-m; therefore, larger values of m offer greater protection against general forgery.A.3 Extension Forgery Based on a CollisionThe underlying idea of extension forgery attacks is for the unauthorized party to find a collision, i.e., two different messages with the same MAC (before any truncation). If the colliding messages are each concatenated with a common string, then, for many MAC algorithms, including RMAC, the two extended messages have a common MAC. Therefore, the knowledge of the MAC of one extended message facilitates the forgery of the other extended message. The unauthorized party can choose the second part of the forged message, i.e., the common string, but generally cannot control the first part, i.e., either of the original, colliding messages.In principle, collisions may exist, because there are many more possible messages than possible MACs. A collision may be detected by the collection and search of a sufficiently large set of message-MAC pairs. By the so-called “birthday surprise” (see, for example, [7]), the size of this sufficiently large set is expected to be, approximately, the square root of the number of possible MAC strings, before any truncation.For RMAC, the extension forgery requires that the salt values, R, are the same for the two colliding messages, as well as the untruncated MACs, i.e., CIPH K3(O n) in the specification of Section 6.3. Therefore, larger values of the block size, b, and the salt size, r, provide greater protection against extension forgery. In particular, the unauthorized party would have to collect at least 2(b+r)/2 message-tag pairs in order to expect to detect a collision.Moreover, if a parameter set is chosen in which m<b, i.e., if CIPH K3(O n) is truncated to produce the MAC, then the discarded bits may be difficult for an unauthorized party to determine, so collisions may be difficult to detect. Parameter sets in which m<b may also provide some protection against other types of attacks.A.4 Summary of Security Properties of Parameter SetsIn Table 2, the expected work factors for the important aspects of the attacks discussed in Sections A.1-A.3 are summarized for the RMAC parameter sets. The values for exhaustive key search are given for the case in which the two RMAC keys are generated from a single master key as discussed in Section B.1.Table 2: Expected Work Factors for Three Types of Attacks on RMACRMAC Parameter Set Exhaustive Key Search(MAC GenerationOperations)General Forgery(Success Probabilityfor a Single Trial )Extension Forgery(Message-Tag Pairs)I 2k-12-32232 (b=64) or 264 (b=128) II 2k-12-64264III 2k-12-80272IV 2k-12-96296V 2k-12-1282128Appendix B: The Generation of RMAC ParametersB.1 Derivation of RMAC keys from a Master KeyThe two secret RMAC keys, K1 and K2, may be derived from a single master key, K, in order to save bandwidth or storage, at the cost of extra invocations of the block cipher to set up the RMAC keys. For example, let CNST1, CNST2, CNST3, CNST4, CNST5, and CNST6 be constants, i.e., fixed, distinct blocks, and let k and b be the key length and block length of the approved block cipher, as before. If k 4 b, then K1 and K2 may be derived from the set of constants as follows:K1=MSB k(CIPH K(CNST1) || CIPH K(CNST3) || CIPH K(CNST5))K2=MSB k(CIPH K(CNST2) || CIPH K(CNST4) || CIPH K(CNST6)).If k=b, then this definition reduces to K1=CIPH K(CNST1) and K2=CIPH K(CNST2), and thus only two constants are actually required.Similarly, if b<k≤2b, then the definition becomes K1= MSB k(CIPH K(CNST1) || CIPH K(CNST3)) and K2=MSB k(CIPH K(CNST2) || CIPH K(CNST4)), and thus only four constants are required.B.2 Salt GenerationThe salt values associated with messages shall repeat with no more than negligible probability. In particular, the expected probability that the same salt will be associated with two different messages that are authenticated under the scope of any pair of RMAC keys shall be no greater than for random values of salt. Therefore, one approach to meeting the requirement is to generate the salt by an approved deterministic random number generator.Another approach is to ensure that the probability of associating the same salt to different messages is zero, in other words, to generate a nonce to be the salt. For example, the salt may be a counter or a message number.Appendix C: Example Vectors for the MAC Generation FunctionIn this appendix, examples vectors are provided for the RMAC MAC generation function with either the AES algorithm or Triple DES as the underlying block cipher. For each allowed key size of the underlying block cipher, MACs are generated on three messages for each parameter set. The lengths of the three messages, denoted Mlen , are 128 bits, 384 bits, and 400 bits. In addition to the MAC for the given input values, intermediate results are provided. All strings are represented in hexadecimal notation.C.1 RMAC-AES128 Example VectorsC.1.1 RMAC-AES128-I RMAC-AES128, r =0, m =32, Mlen =128 M : 000102030405060708090a0b0c0d0e0f K 1: 000102030405060708090a0b0c0d0e0f K 2: 0f0e0d0c0b0a09080706050403020100 R : n o n e M || PAD : 000102030405060708090a0b0c0d0e0f 80000000000000000000000000000000 O_1: 0a940bb5416ef045f1c39458c653ea5a O_n : 3a3807ffe3cb3e978953017210335f0f K 3: 0f0e0d0c0b0a09080706050403020100 CIPH_K 3(O_n ): bfc3c92e04100777be98f7a93e178381 RMAC (R ,M ): bfc3c92e RMAC-AES128, r =0, m =32, Mlen =384 M : 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f K 1: 000102030405060708090a0b0c0d0e0f K 2: 0f0e0d0c0b0a09080706050403020100 R : n o n e M || PAD : 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 80000000000000000000000000000000 O_1: 0a940bb5416ef045f1c39458c653ea5a O_2: 3cf456b4ca488aa383c79c98b34797cb O_3: 7e163e30ea49d32152a51a08a10ec02d O_n : c5b089e3e4710856581f28b42824c651 K 3: 0f0e0d0c0b0a09080706050403020100 CIPH_K 3(O_n ): a3c33ae5f5d19094c5f65faa4ee60696 RMAC (R ,M ): a3c33ae5 RMAC-AES128, r =0, m =32, Mlen =400 M : 000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 3031 K 1: 000102030405060708090a0b0c0d0e0f K 2: 0f0e0d0c0b0a09080706050403020100 R : n o n e M || PAD : 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 30318000000000000000000000000000 O_1: 0a940bb5416ef045f1c39458c653ea5a O_2: 3cf456b4ca488aa383c79c98b34797cb O_3: 7e163e30ea49d32152a51a08a10ec02d O_n : 6a83b72738a946e319702dfd323fae52 K 3: 0f0e0d0c0b0a09080706050403020100 CIPH_K 3(O_n ): 4577d30eac2b9a438e507ecf22cc5fbd RMAC (R ,M ): 4577d30eC.1.2 RMAC-AES128-IIRMAC-AES128, r =0, m =64, Mlen =128 M : 000102030405060708090a0b0c0d0e0f K 1: 000102030405060708090a0b0c0d0e0f K 2: 0f0e0d0c0b0a09080706050403020100 R : n o n e M || PAD : 000102030405060708090a0b0c0d0e0f 80000000000000000000000000000000 O_1: 0a940bb5416ef045f1c39458c653ea5a O_n : 3a3807ffe3cb3e978953017210335f0f K 3: 0f0e0d0c0b0a09080706050403020100 CIPH_K 3(O_n ): bfc3c92e04100777be98f7a93e178381 RMAC (R ,M ): bfc3c92e04100777 RMAC-AES128, r =0, m =64, Mlen =384 M : 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f K 1: 000102030405060708090a0b0c0d0e0f K 2: 0f0e0d0c0b0a09080706050403020100 R : n o n e M || PAD : 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 80000000000000000000000000000000 O_1: 0a940bb5416ef045f1c39458c653ea5a O_2: 3cf456b4ca488aa383c79c98b34797cb O_3: 7e163e30ea49d32152a51a08a10ec02d O_n : c5b089e3e4710856581f28b42824c651 K 3: 0f0e0d0c0b0a09080706050403020100 CIPH_K 3(O_n ): a3c33ae5f5d19094c5f65faa4ee60696。
goodnote untitled(draft)
对于许多人来说,哪种笔记软件是最适合自己的一个让人一直迷惑的问题。
有些人喜欢传统的纸质笔记本,而另一些人则更倾向于使用数字化的笔记软件来记录和管理信息。
在众多笔记软件中,GoodNotes 作为一款备受好评的应用,备受人们的喜爱。
今天我们就来探讨一下GoodNotes 软件的优点和适用场景,希望可以为许多对这款软件感到迷茫的人们提供一些帮助和指导。
1.优点GoodNotes 软件作为一款功能强大的数字化笔记应用,其优点主要体现在以下几个方面:1.1 用户界面简洁友好GoodNotes 软件的界面设计简洁直观,用户可以很快上手,并且无需花费太多时间学习和适应。
这种简洁友好的用户界面设计,让用户能够更加聚焦于笔记的记录和整理,提高了使用效率。
1.2 丰富的功能和工具GoodNotes 软件提供了丰富的功能和工具,比如手写笔记、文字输入、图片插入、PDF标注等,帮助用户更加灵活地进行笔记记录和管理。
而且,这些功能和工具都能够很好地配合使用,让用户可以根据自己的习惯和需求进行个性化的设置和调整。
1.3 强大的文件管理能力GoodNotes 软件具有强大的文件管理能力,用户可以轻松地创建和整理自己的笔记本,快速查找和定位需要的内容,极大地提高了工作效率。
1.4 多评台同步和备份GoodNotes 软件支持多评台同步和备份,用户可以在不同的设备上进行笔记的编辑和查看,而且还能够通过云服务进行数据的备份和恢复,保障了笔记信息的安全性和稳定性。
2.适用场景基于 GoodNotes 软件的优点,我们可以看到它适用的场景也是非常广泛的,主要包括以下几个方面:2.1 学习和教育对于学生和教育工作者来说,GoodNotes 软件是一个非常好的选择。
他们可以利用软件中的丰富功能和工具进行课堂笔记记录、知识整理和学习复习,提高学习效率和成绩水平。
2.2 工作和商务在工作和商务方面,GoodNotes 软件也能够很好地满足用户的需求。
draft1
第一部分项目背景和目标
第一章项目的背景
第二章项目的工作目标
第二部分项目的工作范围和工作方法
第三部分工作报告
第一章宝山城市工业区内外部条件分析
第一节内部优势
1.1 地理位置
1.2 开发区定位、远景规划和政府支持
1.3 外部为开发区提供的配套
第二节内部不利因素
2.1 综述
2.2 配套设施
管委会机构设置及相应机构职能
2.4 招商方法
第三节外部机遇
第四节外部威胁
第二章客户分析
第一节客户分析方法介绍
1.1 工作背景
1.2 主要指标解释(下文这些指标作同样解释)
第二节客户投资地点的选择标准
2.1 投资地点选择标准
2.2 客户选择开发区标准分析
第三节客户选择宝山城市工业园区的原因
第四节客户不选择宝山工业园区的原因
第五节全球最佳实务数据库-成功的工业开发区的特征第三章宝山城市工业园产业发展方向分析
第四章宝山城市工业园区内部营运分析
第一节管理部门组织结构
1.1 结构简介
第二节内部问题分析
内部问题分析方法
2.2 问题分析
第五章战略方向和行动计划
第一节战略方向
1.1 SWOT分析介绍
第二节使命与目标
第三节行动计划。
802.3af标准问题解决方案
• Plenary Activities
– Comment tool
– Resolution process – Comment resolution – New material – Charter drafts
DTE Power via MDI Study Group
• Task Force members must have all comments in before the Plenary
DTE Power via MDI Study Group
802.3af Standard
• Draft 3.0
– Generate during the November Plenary – Based on 2.2 – Changes slides must be presented for all
DTE Power via MDI Study Group
changes between 2.2 & 3.0
• Request approval of 3.0 for WG ballot • Request formation of sponsor pool (IEEE®)
DTE Power via MDI Study Group
802.3af Standard
9/?
11/11
3/10
7/7
8/30
10/31
1/??
5/??
D 1.2
D 2.0
D 2.1 D 2.2
D 3.0
D 3.1
D 3.2
D 4.0
PIBiblioteka PIPI
P
I
P
新疆大专就业协议书
新疆大专就业协议书
Certainly! Here's a draft of the agreement adhering to your specifications:
土石方供应协议书
协议目的与背景
1.1 协议目的
1.2 协议背景
协议方信息
2.1 供应方:姓名:____________________________
2.2 采购方:姓名:____________________________
供应物品描述与规格要求
3.1 供应物品描述
3.2 规格要求与标准
供货期限与交付安排
4.1 供货期限
4.2 交付方式与安排
质量控制与验收标准
5.1 质量控制要求
5.2 验收标准与程序
价格与支付条款
6.1 单价与总价约定
6.2 支付方式与期限
风险责任与保险
7.1 风险转移与责任界定
7.2 保险责任及投保要求
违约与解除条款
8.1 违约责任与后果
8.2 解除协议条件与程序
保密条款
9.1 保密义务及期限
9.2 保密信息范围与例外情况
法律适用与争议解决
10.1 适用法律
10.2 争议解决方式
其他条款
11.1 协议变更与补充
11.2 协议生效及终止
此协议书为示例,具体内容应根据实际需求和情况进行详细填写和调整。
- 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
5
explanation, and the residual position that a large number of growth-retarding factors suddenly happened to hit at once is unlikely.7
3 4
See, for example, Kosterlitz (2002). See Gordon (2002) and Gordon (2000). 5 See Basu, Fernald, and Shapiro (2001). 6 See Greenwood and Jovanovic (1999).
The causes of the productivity slowdown of the 1973-1995 or so period remain disappointingly mysterious. Baily (2002) calls the growth-accounting literature on the slowdown “large but inconclusive.” No single factor provides a convincing and coherent
In the second half of the 1990s American productivity picked itself up, and more-or-less resumed its pre-1973 pace. Between the beginning of 1995 and the semi-official NBER business cycle peak in March 2001, U.S. nonfarm-business output per person-hour worked grew at an annual rate of 2.80 percent per year. (Extending the sample through the 2001 recession to the likely trough point of 2001:4, the late-1990s growth rate is 2.69
2
பைடு நூலகம்Abstract
The causes of the productivity growth slowdown of the 1970s remain mysterious. By contrast, nearly all agree that the cause of the productivity growth speed-up of the 1990s lie in the information technology sector. The extraordinary pace of invention and innovation in the information technology sector has generated real price declines of between ten and twenty percent per year for decades. Increased total factor productivity in the information technology capital goods-producing sector coupled with extraordinary real capital deepening as the quantity of real investment in information technology capital bought by a dollar of nominal savings grows have together driven the productivity growth acceleration of the later 1990s. Will this new, higher level of productivity growth persist? The answer appears likely to be “yes.” The most standard of simple applicable growth models—that of Oliner and Sichel—predicts that the social return to information technology investment would have to suddenly and discontinuously drop to zero for the upward jump in productivity growth to reverse itself in the near future. More complicated models that focus in more detail on the determinants of investment spending or on the sources of increased total factor productivity appear to strengthen, not weaken, forecasts of productivity growth over the next decade.
2
See Krugman (1994) for one interpretation of how the productivity slowdown made a big difference.
4
percent per year.) Between the beginning of 1995 and the semi-official NBER business cycle peak in March 2001, U.S. real GDP grew at a pace of 4.21 percent per year. (Extending the sample through the 2001 recession to the likely trough point of 2001:4, the late-1990s growth rate is 3.85 percent per year.) Non-economists tended to attribute a large chunk of fast late-1990s growth to “cyclical” factors, 3 but economists had a much harder time attributing more than a few tenths of a percentage point per year of late1990s growth to the business cycle.4 Moreover, as Susanto Basu, John Fernald, and Matthew Shapiro have powerfully argued, there are stronger reasons for thinking that the adjustment costs associated with moving to a more information technology capitalintensive growth path led actual growth to understate trend growth than for thinking that cyclical factors led actual growth to overstate trend growth in the second half of the 1990s.5 And the extremely rapid run-up of stock prices indicated that at least the marginal investor in equities anticipated that the acceleration of economic growth that started in the mid-1990s would last for decades or longer.6
Productivity Growth in the 2000s
J. Bradford DeLong1 University of California at Berkeley and NBER
March 2002
Draft 1.2
1
I would like to thank the University of California at Berkeley for financial support, and Chad Jones, Dan Sichel, and Larry Summers for helpful discussions.
3
I. Introduction
In the early 1970s, U.S. productivity growth fell off a cliff. Measured output per personhour worked in nonfarm business had averaged a growth rate of 2.88 percent per year from 1947 to 1973. It averaged a growth rate of only 1.30 percent per year from 1973 to 1995. The deceleration in the growth rate of total real GDP was somewhat smaller: a matter of –1.18 percentage points per year in output rather than the -1.58 percentage points per year in labor productivity, as total real GDP growth slowed from 3.91 percent per year averaged over 1947:1 to 1973:2 to 2.73 percent per year averaged real over 1973:2 to 1995:1. The social changes that brought more women into the paid labor force in enormous numbers cushioned the effect of this productivity slowdown on the growth rate of measured total real GDP, if not its effect on Americans’ material welfare. The productivity slowdown meant that, according to official statistics, Americans in 1995 were only 70 percent as productive as their predecessors back in the early 1970s would have expected them to be. The productivity slowdown gave rise to an age of diminished expectations that had powerful although still debated effects on American politics and society.2