面向安全 AI 智能体发现的智能体名称服务_第1页
面向安全 AI 智能体发现的智能体名称服务_第2页
面向安全 AI 智能体发现的智能体名称服务_第3页
面向安全 AI 智能体发现的智能体名称服务_第4页
面向安全 AI 智能体发现的智能体名称服务_第5页
已阅读5页,还剩91页未读, 继续免费阅读

下载本文档

版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领

文档简介

SECURITY

PROJECT

ANDGENERATIVEAl

才OWASP.

GenAI

TOP10FORLLM

AgentNameService(ANS)forSecureAlAgent

Discovery

TowardsSecureandInteroperableAgenticAl:

DNSforAlAgents

Version1.0

May13,2025

Theinformationprovidedinthisdocumentdoesnot,andisnotintendedto,constitutelegaladvice.All

informationisforgeneralinformationalpurposesonly.Thisdocumentcontainslinkstootherthird-partywebsites.SuchlinksareonlyforconvenienceandOWASPdoesnotrecommendorendorsethecontentsofthethird-partysites.

LicenseandUsage:

ThisdocumentislicensedunderCreativeCommons,CCBY-SA4.0Youarefreeto:

●Share-copyandredistributethematerialinanymediumorformat

●Adapt-remix,transform,andbuilduponthematerialforanypurpose,evencommercially.

●Underthefollowingterms:oAttribution-Youmustgiveappropriatecredit,providealinktothelicense,andindicateifchangesweremade.Youmaydosoinanyreasonablemannerbutnotinanywaythat

suggeststhelicensorendorsesyouoryouruse.oAttributionGuidelines-mustincludetheprojectnameaswellasthenameoftheassetReferenced:OWASPGenAISecurityProject-AgenticSecurityInitiative:AgenticAl-AgentNameService(ANS)forSecureAlAgentDiscovery

●ShareAlike-Ifyouremix,transform,orbuilduponthematerial,youmustdistributeyourcontributionsunderthesamelicenseastheoriginal.

Linktofulllicensetext:

/licenses/by-sa/4.0/legalcode

OWASP.orgPage1

TableofContent

Abstract4

1.Introduction5

2.RelatedWork6

3.AgentRegistryArchitecture7

3.1AgentRegistrationandRenewal10

3.2PKIIntegration11

3.3ANSProtocolNotation12

3.4Protocol-AgnosticCommunicationSchema14

3.5ANSNamingStructureandResolution16

3.6ANSChallengesandGovernance22

3.7AgentIdentity23

4.Request/ResponseSchemaforANSNameResolution28

5.ProtocolAdapterLayer31

5.1A2AProtocolAdapter31

5.2MCPAdapter32

OWASP.orgPage2

OWASP.orgPage3

5.3ACPAdapter 5.4ExtensionPoints32 5.5Cross-ProtocolInteroperabilityLimits32 5.6ProtocolAdapterAPIDefinition336.SecurityAnalysisandConsiderations35 6.1MAESTRO-BasedThreatAnalysis35 6.2AdditionalSecurityControlsandConsiderations377.ImplementationConsiderations398.FutureConsiderations42Acknowledgements44

OWASPTop10forLLMProjectSponsors45

ProjectSupporters46

References48

AppendixA:CompleteRequest/ResponseSchemas49

AppendixB:GlossaryofTerms-AgentNameService(ANS)50

OWASP.orgPage4

Abstract

TheproliferationofAlagentsrequiresrobustmechanismsforsecurediscovery.ThispaperintroducestheAgentNameService(ANS),anovelarchitecturebasedonDNSaddressingthelackofapublicagent

discoveryframework.ANSprovidesaprotocol-agnosticregistrymechanismthatleveragesPublicKeyInfrastructure(PKI)certificatesforverifiableagentidentityandtrust.

Thearchitecturefeaturesseveralkeyinnovations:aformalizedagentregistrationandrenewalmechanismforlifecyclemanagement;DNS-inspirednamingconventionswithcapability-awareresolution;amodular

ProtocolAdapterLayersupportingdiversecommunicationstandards(A2A,MCP,ACP,etc.);andprecisely

definedalgorithmsforsecureresolution.WeimplementstructuredcommunicationusingJSONSchemaandconductacomprehensivethreatanalysisofourproposal.

Theresultisafoundationalagentdirectoryserviceprotocoladdressingthecorechallengesofsecure

discoveryandinteractioninmulti-agentsystems,pavingthewayforfutureinteroperable,trustworthy,andscalableagentecosystems.

Keywords:AgentNameService(ANS),AgenticAI,ServiceDiscovery,PublicKeyInfrastructure(PK),Interoperability,SecureDNS,FormalMethods,Multi-AgentSystems(MAS)

OWASP.orgPage5

1.Introduction

Agent-to-agentcommunicationisexpectedtobecomeasignificantcomponentofinternettraffic,drivingtheneedforreliablemechanismsenablingagentstodiscover,verify,andsecurelyinteractwithoneanother.Traditionalservicediscovery,notablytheDomainNameSystem(DNS)[RFC1035,1987],primarilymaps

human-readablenamestonetworkaddressesandisinsufficientforthedynamic,semanticallyrich,and

security-sensitiveenvironmentofagenticAI.EnhancementslikeDNS-BasedServiceDiscovery(DNS-SD)

[RFC6763,2013]offerimprovementsbutstillfallshortofthenecessaryagentcapabilitygranularity,identityverification,andlifecyclemanagementrequiredbyautonomousagents.Furthermore,maintaininga

trustworthyregistrynecessitatesrobustprocessesforagentregistrationandperiodicrenewal.

Severalagentcommunicationprotocolsareemergingtostandardizeinteractions:

·Agent2Agent(A2A)Protocol[Surapanenietal.,2025]:DevelopedbyGoogle,providinga

standardizedprotocolforinter-agentcommunication,aimingtobridgedifferentagentframeworks.

·ModelContextProtocol(MCP)[Anthropic,2024;MCPSpecification,2025]:FocusedonsimplifyingtheintegrationofAlmodelswithexternaltoolsanddatasources.

·AgentCommunicationProtocol(ACP)[IBMResearch,2025]:Designedtostandardizehowagentscommunicate,enablingautomation,collaboration,Ulintegration,anddevelopertooling,evolvingfrominitialMCPconcepts.

ThispaperoutlinestheAgentNameService(ANS),aframeworkforaprotocol-agnosticAgenticAIRegistry.ANScomplementstheseemergingprotocolsbyintegratingPublicKeyInfrastructure(PKI)foridentityandtrust,definingstructuredcommunicationviaJSONSchema,incorporatingDNS-likenamingfordiscovery,establishingmechanismsforagentregistrationandrenewal,andprovidingaformalspecificationofthe

protocoltoenhanceprecisionandimplementability.ANSaimstoprovideauniversal,securedirectoryservicefoundationforinteroperableagentecosystems.

OWASP.orgPage6

2.RelatedWork

Traditionalservicediscovery,likeDNS[RFC1035,1987],providesessentialname-to-addressresolutionbutlacksthesemanticunderstandingandsecurityfeaturesneededforagenticAI.DNS-SD[RFC6763,2013]addslocalservicediscoverycapabilitiesbutdoesn'taddressverifiableidentityorcomplexagentCapabilitymatchingonaglobalscale.

Researchinmulti-agentsystems(MAS)hasexploredvariousagentcommunicationlanguages(ACLs),suchasthosedefinedbytheFoundationforIntelligentPhysicalAgents(FIPA)[FIPA,2002].Whileinfluential,

theseoftenlackstandardized,built-insecuritymechanismsanduniversallyadoptedtransportprotocolssuitableforthemoderninternet.

Theemergingprotocolsrepresentsignificantadvancements:

·A2A[Surapanenietal.,2025]focusesonbridgingagentecosystems.

·MCP[Anthropic,2024;MCPSpecification,2025]emphasizescontextandintegrationoftools/dataforAlmodels.

·ACP[IBMResearch,2025]targetsbroaderagent-to-agentcommunicationneeds,includingdelegationandorchestration.

Ourworkbuildsupontheseeffortsnotbyreplacingthem,butbyprovidingacomplementary,protocol-

agnosticinfrastructurelayer.ANSdifferentiatesitselfbyintegratingPKl-basedidentityverificationdirectlyintothediscoveryandlifecyclemanagementprocess,offeringauniversalregistrymechanismthat

enhancestrustandfacilitatessecureinteractionacrossdifferentprotocolstandardsviaacommon

discoveryplan.Furthermore,theformalizedspecificationoftheANSprotocolensuresclarityandeaseofimplementation.

OWASP.orgPage7

3.AgentRegistryArchitecture

TheproposedAgentRegistryarchitectureprovidesasecure,interoperableplatformforagentdiscoveryandinteraction,supportingmultiplecommunicationprotocolsthroughamodulardesign.Keycomponents

include:

·RequestingAgent:Theentityinitiatingtheagentregistrationprocess,whichcouldbeanindividual,organization,orautomatedsystemseekingtoregisteranewagentorupdateexistingagent

informationintheregistry.

·AgentRegistry:ApotentiallydistributeddatabaseforstoringACEM(AgentCredentialand

EntitlementManagement)andDID(DecentralizedIdentifier)relatedinformation.Thisregistry

encompassesagentcapabilities,securitypolicies,PKIcertificates,protocol-specificmetadata(viaprotocolExtensions),andregistration/renewaltimestamps,supportingacomprehensiveframeworkforagentidentity,authentication,andauthorization.

·CertificateAuthority(CA):AtrustedentityissuingandmanagingX.509digitalcertificates[RFC5280,2008]foragents,formingtherootoftrust.

·RegistrationAuthority(RA):Verifiesagentregistration/renewalrequests,interactswiththeCAtoissuecertificatesbasedonCertificateSigningRequests(CSRs),andmanagestheagentlifecycle(registration,renewal,revocation).ItenforcesregistrypoliciesandvalidatesthelegalentityoftheRequestingAgent.

·ProtocolAdapterLayer:Translatesbetweentheregistry'sinternalrepresentationandprotocol-specificformats(detailsinSection5).

·Request/ResponseSchema:Aprotocol-agnosticJSON-basedschemaforregistryinteractions(discovery,registration,etc.),incorporatingPKIdataandallowingprotocol-specificextensions(detailsinSection4)

·AgentNameService(ANS):Enablesagentdiscoveryusinghuman-readable,structurednames,coupledwithagentCapability-basedresolution(detailsinSection3.5).

Figure1illustratesthecorecomponentsoftheAgentNameService(ANS)andhowtheyinteract.ImagineanAgenttryingtofindanotheragent.ItstartsbycontactingtheANSService,whichactslikeacentral

directory.TheANSServicereliesontheAgentRegistry,aspecializeddatabasecontaininginformationabout

OWASP.orgPage8

allregisteredagents,includingtheircapabilities,securitypolicies,andcontactdetails.TheAgentRegistryalsointeractswithaCertificateAuthority(CA),whichissuesandmanagesdigitalcertificatestoverifyagentidentities,andaRegistrationAuthority(RA),whichvalidatesnewagentsjoiningthesystem.Tosupport

differentcommunicationprotocols,theANSServiceusesaProtocolAdapterLayer,whichtranslates

requestsandresponsesintotheappropriateformat.AllcommunicationwithANSservicesisstructuredwithJSONschemas.Together,thesecomponentsformtheAgentRegistryInfrastructurethatallowssecureandreliableagentdiscovery.

TheProtocolAdapterLayertranslatesbetweentheregistry'sinternalrepresentationandprotocol-specificformats.Forexample,consideranagentregisteringwiththeMCP.AnMCPtooldescriptionmightbe

representedasaJSONblob.Critically,theagentwouldneedtoberegisteredwithANSfirstandforemost.Therefore,imaginethistoolisassociatedwiththefollowingANSName

"mcp://sentimentAnalyzer.textAnalysis.ExampleCorp.v1.0".ThiswouldmeantheMCPtoolisnowdiscoverableviatheANS.TheMCPspecificextensiondataitselfmightlooklikethis:

"description":"Analyzessentimentoftextinput.","input_schema":{

"type":"string",

"description":"Texttoanalyze."

"output_schema":{"type":"object","properties":{

"sentiment":{"type":"string",

"enum":["positive","negative","neutral"]

"score":{

"type":"number",

"description":"Sentimentscore(-1to1).

"mcpEndpoint":"

"

/analyze"

TheMCPAdapterwithintheProtocolAdapterLayerwouldparsethisJSONandmapittotheregistry'sinternalcolumns.Thiscouldinvolve:

·Extractinginformationimplicitly:sincetheANSNameis

"mcp://sentimentAnalyzer.textAnalysis.ExampleCorp.v1.0",thisimplicitlydefinesthe:

·Protocol:mcp

·AgentID:sentimentAnalyzer

OWASP.orgPage9

·agentCapability:textAnalysis

·Provider:ExampleCorp

●Version:v1.0

·Storingthedescription("Analyzessentimentoftextinput.")inadedicateddescriptionfieldwithinprotocolExtensions.

·Serializingtheinput_schemaandoutput_schemaandstoringtheminaprotocolExtensionscolumnspecifictoMCP,allowingotherMCP-awareagentstounderstandthetool'sinterface.

·TheactualMCPendpoint"

wouldbestoredwithintheprotocolExtensions"

/analvze"wouldbestoredwithinthe

wouldbestoredwithintheprotocolExtensions"

protocolExtensions

,

under

thekeymcpEndpoint.

ThisnormalizationprocessallowstheAgentRegistrytostoreandqueryMCP-specificinformationinaprotocol-agnosticway,whileadheringtotheANSNamestructureforconsistentidentificationand

resolution.

Verifiesidentity

AgentRegistry

CertificateAuthority

AgentRequestsagentdiscoveryANSServiceLooksupagentinformation.

Validates

registration

Translatesmessages

RegistrationAuthority

ProtocolAdapter

Layer

Figure1-ANSArchitecture

Table1outlineshowGoogleA2AAnthropicMCP,andIBM'sACPvalidateagentsandenforcesecuritywithintheANS.Eachprotocolusesdistinctadapterimplementationsandvalidationmechanisms-suchasZKPs

(Zero-KnowledgeProofs),toolschemachecks,androle-basedcontrols-toensuretrustedidentity,

capabilityverification,andsecureagentinteractions.Zero-KnowledgeProofs(ZKPs)arecryptographic

protocolsthatallowoneparty(theprover)toconvinceanotherparty(theverifier)thatastatementistrue

withoutrevealinganyinformationbeyondthevalidityofthestatementitself.Theseprotocolsmaintainthree

essentialproperties:completeness(avalidproofalwaysconvincesanhonestverifier),soundness(afalsestatementcannotbeproventrueexceptwithnegligibleprobability),andzero-knowledge(theverifierlearnsnothingbeyondthestatement'svalidity).ZKPscanbeusedforcapabilityattestationbyenablingagentstoprovetheypossesscertainabilitiesorskillswithoutexposingtheunderlyingdata..

PROTOCOL

ADAPTERIMPLEMENTATION

VALIDATIONMECHANISM

SECURITYFEATURES

GoogleAgent

(Agent2Agent)

NativelmplementationwithGoogleSDK

AgentIDcardIntegrityverification.

CapabilityattestationwithZKP

AnthropicMCP

Anthropiccompliantadapterwithextensionvalidation

ToolIdentity/

ToolSchemaverification

Resourceaccesscontrol

ACP(Agent

communicationProtocol)

IBMACPReferenceImplementation

Role-basedAgentIdentifyand

capabilityenforcement

Delegationvalidation

3.1AgentRegistrationandRenewal

Maintainingregistryintegrityrequiresexplicitlifecyclemanagement:

·Registration:

1.Anagentsubmitsaregistrationrequest(conformingtothedefinedJSONschema)includingmetadata,protocoldetails(withinprotocolExtensions),andaCSR.

2.TheRAvalidatestheagent'sidentityandsubmittedinformationagainstregistrypolicies(potentiallyinvolvingautomatedchecksorhumanreview).

3.TheRArequestsacertificatefromtheCAusingthevalidatedCSR.

4.TheissuedcertificateandagentinformationarestoredintheAgentRegistry.

·Renewal:

1.Agentsperiodicallysubmitrenewalrequestsbeforetheirregistrationorcertificateexpires.

2.TheRAverifiescontinuedcompliancewithpolicies.

OWASP.orgPage10

3.TheRArequestsanewcertificatefromtheCA.

4.Theagent'sregistration/renewaltimestampandpotentiallyupdatedcertificatearestoredintheRegistry.

·Deregistration/Revocation:Agentscanbederegistered,ortheircertificatesrevoked(e.g.,duetokeycompromise),removingorflaggingtheirentryintheregistryandinvalidatingtheircertificateviastandardPKImechanisms(CRL/OCSP).

Figure2outlinesthestepsanagenttakestoregisterwiththeAgentNameService(ANS).The

processbeginswhenanAgentsendsaRegistrationRequesttotheRegistrationAuthority(RA).Thisrequestincludestheagent'smetadata(name,capabilities,etc.)andaCertificateSigningRequest(CSR).TheRAthenValidatestheagent'sidentityandinformation.IfthevalidationFails,the

RegistrationisRejected.IfthevalidationisSuccessful,theRArequestsaCertificatefromthe

CertificateAuthority(CA).TheCAissuesthecertificateandsendsitbacktotheRA..Finally,theRAstorestheagent'sinformationandcertificateintheAgentRegistryandsendsaConfirmationbacktotheAgent,completingtheregistrationprocess.

AgentRegistrationAuthorityCertificateAuthority

RegistrationRequest(metadata&CSR)

Validatesagent'sidentityandinformation

alt[ValidationFails]

RegistrationRejected

[ValidationSuccessful]

RequestCertificate

IssueCertificate

Storeagentinfoandcertificate

Confirmation

AgentRegistrationAuthorityCertificateAuthority

AgentRegistry

AgentRegistry

Figure2:AgentRegistrationProcess

3.2PKIIntegration

OWASP.orgPage11

PKI[RFC5280,2008]providesthefoundationfortrust.EachregisteredagentpossessesauniquePKlkeypairandacorrespondingdigitalcertificateissuedbytheCAviatheRA.

·IdentityVerification:Thecertificatebindstheagent'spublickeytoitsverifiedidentity(e.g.,its

ANSName,organizationalaffiliation).Otheragentscanverifysignaturesmadewiththeprivatekeyusingthepublickeyinthecertificate,ensuringauthenticityandintegrity.

·TrustChain:CertificatesarevalidatedagainstthetrustedCA,establishingachainoftrust.

·LifecycleManagement:Certificatevalidityistiedtotheregistration/renewalcycle.Revoked

certificatesarehandledusingCertificateRevocationLists(CRLs)ortheOnlineCertificateStatusProtocol(OCSP)[RFC6960,2013].

·Simplification:WhilePKlmanagementcanbecomplex,theRA/CAinteractionwithintheregistryframeworkaimstostreamlinecertificateissuanceandrenewalforagentdeveloperscomparedtomanualprocesses.

3.3ANSProtocolNotation

WeintroducethefollowingnotationfordefiningANSelementsandoperations:

3.3.1TopLevelElements

·Protocol:CommunicationProtocol

·AgentID:AgentIdentifier

·agentCapability:AgentCapability

·Provider:ProviderName

·Version:VersionNumber

·Extension:ExtensionMetadata

·Cert:AgentCertificate(X.509)

·Sig:DigitalSignature

·ANSName:AgentNameServiceName

·Endpoint:aresolvableendpoint

3.3.2DataTypes:

OWASP.orgPage12

OWASP.orgPage13

·String:Representsasequenceofcharacters.

·Integer:Representsanintegernumber.

·Boolean:Representsabooleanvalue(trueorfalse).

·Set<T>:RepresentsasetofelementsoftypeT.

So,thetoplevelelementshavethefollowingdatatypes:

·Protocol:{a2a,mcp,acp,...//Enumeratedsetofprotocols

·AgentID:String

·agentCapability:String

·Provider:String

·Version:String(SemanticVersioning)

·Extension:String

·Cert:X.509Certificate

·Sig:DigitalSignature

·ANSName:String//Formattedstringasdefinedbelow

·Endpoint:String//Networkaddress,servicebinding

3.3.3VerificationRules

CertificateChainVerification

VerifyCertChain(Cert,TrustedCA)->Boolean:

1.Getthecertificateauthority(CA)thatsignedtheCert

2.CheckforCertificateRevocationstatusofCertviaCRLorOCSP

3.IfCertisRevokedReturnFalse

4.IfCA==TrustedCA,ReturnTrue

5.Else,recursivelycheckCACertagainstTrustedCA

6.IfnotrustedCAisfoundinthechain,ReturnFalse

OWASP.orgPage14

DigitalSignatureVerification

VerifySignature(Data,Signature,PublicKey)->Boolean:

1.UsePublicKeytodecrypttheSignature

2.HashDatausingagreeduponfunction(e.g.,SHA-256)

3.ComparethedecryptedsignaturetotheDatahash

4.IfsignaturesarevalidreturnTrue,otherwisereturnFalse

3.4Protocol-AgnosticCommunicationSchema

WedefineJSONSchema[RFC7159,2014]documentsforregistryinteractions(discoveryrequests/responses,registration/renewalrequests/responses).Thisensuresstructured,validatablecommunication.

AnexampleAgentRegistrationRequestschema:

"$schema":"

,"

http://json-schema.org/draft-07/schema#",

"title":"AgentRegistrationRequest",

"description":"SchemaforAgentRegistrationRequest","type":"object",

"properties":{"protocol":{

"type":"string",

"enum":["a2a","mcp","acp"],

"description":"CommunicationProtocol"

"agentID":{

"type":"string"description":

"

,

"UniqueAgentIdentifier"

"agentCapability":{

"type":"string",

"description":"PrimaryAgentCapability"

"provider":{

"type":"string",

"description":"NameoftheProvider""version":{

e:"s:in(|[,-9]\\d*)\1.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-((?:0|[1-

9]\\d*\\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\\d*\\d*[a-zA-Z-][0-9a-ZA-Z-

OWASP.orgPage15

]*))*))?(?:\+([0-9a-zA-Z-]+(?:\\.[0-9a-zA-Z-]+)*))?$",

"description":"SemanticVersioningformat"

"extension":{

"type":"string",

"description":"ExtensionMetadata"

"certificate":{

"type":"object",

"properties":{

"subject":{

"type":"string",

"description":"CertificateSubject"

"issuer":{

"type":"string",

"description":"CertificateIssuer"

"pem":{

"type":"string",

"description":"PEM-encodedCertificate(stronglyrecommendedtouseasecurevaultreferenceinstead)",

"readonly":false

"required":["subject","issuer","pem"]

"protocolExtensions":{"type":"object",

"description":"Protocol-specificdata"

"required":["protocol","agentID","a"certificate"]

gentCapability","provider","version",

·CoreFields:Includecommonelementslikeagentcommunicationprotocoltypessuchasa2a,mcp,andacp,etc,requesting/respondingagentidentifiers,timestamps,andPKIcertificatedetails

(subject,issuer,PEMrepresentation-thoughreferencingasecurevaultisrecommendedforthePEMinproduction).

·protocolExtensions:Akeyfieldwithintheschemaactsasacontainerforprotocol-specificdata

(e.g.,anA2AAgentCard,MCPtooldescriptions,ACPagentprofiles).Thisallowstheregistrytostoreandqueryprotocol-specificagentCapabilitieswhilemaintainingacommoncoreschema.

·Validation:Allinteractionswiththeregistrymustbevalidatedagainsttheseschemas.(SeeSection

4formoredetailsontheschemastructure).

3.5ANSNamingStructureandResolution

ANSdefinesarobust,protocol-agnosticmechanismfornamingandresolvingagentsacross

heterogeneousagenticenvironments.ItsprincipalfunctionistoestablishauniformEndpoint

formatthatencodesidentity,agentCapability,andcontextualmetadataforanygivenagent,

irrespectiveoftheunderlyingtransportorruntimearchitecture.ANSensuresthatbothhuman-

readableandmachine-resolvableidentifiersarepreservedinaformatdesignedtofacilitate

dynamicdiscovery,rigoroustrustverification,securecommunication,seamlessservice

composition,andtherepresentationofrelationshipsbetweenagents.AkeymotivationforANSistomovebeyondsimplenamingresolutiontoenablepreciseagentCapabilitydiscovery,whichisnot

achievablewithtraditionalsystemslikeDNS.ThedesignofANSacknowledgesthattheagent's

agentCapabilitiesareparamou

温馨提示

  • 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
  • 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
  • 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
  • 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
  • 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
  • 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
  • 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

评论

0/150

提交评论