Network Working Group R. Sofia Request for Comments: 3795 P. Nesser, II Category: Informational Nesser & Nesser Consulting June 2004 Survey of IPv4 Addresses in Currently Deployed
IETF Application Area Standards Track and Experimental Documents Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2004).
Abstract
This document describes IPv4 addressing dependencies in an attempt to clarify the necessary steps in re-designing and re-implementing
specifications to become network address independent, or at least, to dually support IPv4 and IPv6. This transition requires several
interim steps, one of them being the evolution of current IPv4
dependent specifications to a format independent of the type of IP
addressing schema used. Hence, it is hoped that specifications will be re-designed and re-implemented to become network address
independent, or at least to dually support IPv4 and IPv6.
To achieve that step, it is necessary to survey and document all IPv4 dependencies experienced by current standards (Full, Draft, and
Proposed) as well as Experimental RFCs. Hence, this document
describes IPv4 addressing dependencies that deployed IETF Application Area documented Standards may experience.
Sofia & Nesser II Informational [Page 1]
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Document Organization. . . . . . . . . . . . . . . . . . . . . 2
3. Full Standards . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Draft Standards. . . . . . . . . . . . . . . . . . . . . . . . 5
5. Proposed Standards . . . . . . . . . . . . . . . . . . . . . . 10
6. Experimental RFCs. . . . . . . . . . . . . . . . . . . . . . . 34
7. Summary of Results . . . . . . . . . . . . . . . . . . . . . . 45
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 47
9. Security Considerations. . . . . . . . . . . . . . . . . . . . 48
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48 10.1. Normative References. . . . . . . . . . . . . . . . . . 48
10.2. Informative References. . . . . . . . . . . . . . . . . 48
11. Authors’ Addresses . . . . . . . . . . . . . . . . . . . . . . 49
12. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 50 1. Introduction
The exhaustive documentation of IPv4 addresses usage in currently
deployed IETF documented standards has now been broken into seven
documents conforming to current IETF main areas, i.e., Applications, Internet, Operations and Management, Routing, Sub-IP, and Transport.
A general overview of the documentation, as well as followed
methodology and historical perspective can be found in [1]. This
document represents one of the seven blocks, and its scope is limited to surveying possible IPv4 dependencies in IETF Application Area
documented Standards.
2. Document Organization
The remainder sections are organized as follows. Sections 3, 4, 5,
and 6 describe, respectively, the raw analysis of Internet Standards [2]:
Full, Draft, and Proposed Standards, and Experimental RFCs. For each section, standards are analysed by their RFC number, in sequential
order, i.e., from RFC 1 to RFC 3200. Exceptions to this are some
RFCs above RFC 3200. They have been included, given that they
obsoleted RFCs within the range 1-3200. Also, the comments presented for each RFC are raw in their nature, i.e., each RFC is simply
analysed in terms of possible IPv4 addressing dependencies. Finally, Section 7 presents a global overview of the data described in the
previous sections, and suggests possible future steps.
Sofia & Nesser II Informational [Page 2]
3. Full Standards
Internet Full Standards have attained the highest level of maturity
on the standards track process. They are commonly referred to as
"Standards", and represent fully technical mature specifications that are widely implemented and used throughout the Internet.
3.1. RFC854: Telnet Protocol Specifications
There are no IPv4 dependencies in this specification.
3.2. RFC 855: Telnet Option Specifications
There are no IPv4 dependencies in this specification.
3.3. RFC 856: Binary Transmission Telnet Option
There are no IPv4 dependencies in this specification.
3.4. RFC 857: Echo Telnet Option
There are no IPv4 dependencies in this specification.
3.5. RFC 858: Suppress Go Ahead Telnet Option
There are no IPv4 dependencies in this specification.
3.6. RFC 859: Status Telnet Option
There are no IPv4 dependencies in this specification.
3.7. RFC 860: Timing Mark Telnet Option
There are no IPv4 dependencies in this specification.
3.8. RFC 861: Extended Options List Telnet Option
There are no IPv4 dependencies in this specification.
3.9. RFC 862: Echo Protocol
There are no IPv4 dependencies in this specification.
3.10. RFC 863: Discard Protocol
There are no IPv4 dependencies in this specification.
Sofia & Nesser II Informational [Page 3]
3.11. RFC 864: Character Generator Protocol
There are no IPv4 dependencies in this specification.
3.12. RFC 865: Quote of the Day Protocol
There are no IPv4 dependencies in this specification.
3.13. RFC 866: Active Users Protocol
There are no IPv4 dependencies in this specification.
3.1
4. RFC 867: Daytime Protocol
There are no IPv4 dependencies in this specification.
3.15. RFC 868: Time Server Protocol
There are no IPv4 dependencies in this specification.
3.16. RFC 959: File Transfer Protocol
Section 4.1.2 (TRANSFER PARAMETER COMMANDS) describes the port
command using the following format:
"A port command would be:
PORT h1,h2,h3,h4,p1,p2
where h1 is the high order 8 bits of the internet host
address."
This is a clear reference to an IPv4 address. In sections 4.2.1 and 4.2.2, on reply codes, the code:
"227 Entering Passive Mode (h1,h2,h3,h4,p1,p2)"
also needs to be reworked for IPv6 addressing. Also, Section 5.3.2
(FTP COMMAND ARGUMENTS) contains:
"
This needs to be solved to transition to IPv6.
3.17. RFC 1350: Trivial File Transfer Protocol
There are no IPv4 dependencies in this specification.
Sofia & Nesser II Informational [Page 4]
3.18. RFC 1870: SMTP Service Extension for Message Size
Declaration
There are no IPv4 dependencies in this specification.
3.19. RFC 1939: Post Office Protocol - Version 3
There are no IPv4 dependencies in this specification.
3.20. RFC 2920: SMTP Service Extension for Command Pipelining
There are no IPv4 dependencies in this specification.
4. Draft Standards
Draft Standards is the nomenclature given to specifications that are on the penultimate maturity level of the IETF standards track
process. They are considered to be final specifications, which may
only experience changes to solve specific problems found. A
specification is only considered to be a Draft Standard if there are at least two known independent and interoperable implementations.
Hence, Draft Standards are usually quite mature and widely used.
4.1. RFC 954: NICNAME/WHOIS
There are no IPv4 dependencies in this specification.
4.2. RFC 1184: Telnet Linemode Option
There are no IPv4 dependencies in this specification.
4.3. RFC 1288: The Finger User Information Protocol
There are no IPv4 dependencies in this specification.
4.4. RFC 1305: Network Time Protocol (Version 3) Specification,
Implementation
Section 3.2.1 (Common Variables) provides the following variable
definitions:
"Peer Address (peer.peeraddr, pkt.peeraddr), Peer Port
(peer.peerport, pkt.peerport): These are the 32-bit Internet
address and 16-bit port number of the peer.
Sofia & Nesser II Informational [Page 5]
Host Address (peer.hostaddr, pkt.hostaddr), Host Port
(peer.hostport, pkt.hostport): These are the 32-bit Internet
address and 16-bit port number of the host. They are included
among the state variables to support multi-homing."
Section 3.4.3 (Receive Procedure) defines the following procedure:
"The source and destination Internet addresses and ports in the IP and UDP headers are matched to the correct peer. If there is no
match a new instantiation of the protocol machine is created and
the association mobilized."
Section 3.6 (Access Control Issues) proposes a simple authentication scheme in the following way:
"If a more comprehensive trust model is required, the design can
be based on an access-control list with each entry consisting of a 32-bit Internet address, 32-bit mask and three-bit mode. If the
logical AND of the source address (pkt.peeraddr) and the mask in
an entry matches the corresponding address in the entry and the
mode (pkt.mode) matches the mode in the entry, the access is
allowed; otherwise an ICMP error message is returned to the
requestor. Through appropriate choice of mask, it is possible to restrict requests by mode to individual addresses, a particular
subnet or net addresses, or have no restriction at all. The
access-control list would then serve as a filter controlling which peers could create associations."
Appendix B Section 3 (B.3 Commands) defines the following command:
"Set Trap Address/Port (6): The command association identifier,
status and data fields are ignored. The address and port number
for subsequent trap messages are taken from the source address and port of the control message itself. The initial trap counter for trap response messages is taken from the sequence field of the
command. The response association identifier, status and data
fields are not significant. Implementations should include sanity timeouts which prevent trap transmissions if the monitoring
program does not renew this information after a lengthy interval." The address clearly assumes the IPv4 version. Also, there are
numerous places in sample code and in algorithms that use the above
mentioned variables. It seems that there is no reason to modify the actual protocol. A small number of textual changes and an update to implementations, so they can understand both IPv4 and IPv6 addresses, will suffice to have a NTP version that works on both network layer
protocols.
Sofia & Nesser II Informational [Page 6]
4.5. RFC 1575: An Echo Function for CLNP (ISO 8473)
There are no IPv4 dependencies in this specification.
4.6. RFC 1652: SMTP Service Extension for 8bit-MIME Transport
There are no IPv4 dependencies in this specification.
4.7. RFC 1832: eXternal Data Representation Standard
There are no IPv4 dependencies in this specification.
4.8. RFC 2045: Multipurpose Internet Mail Extensions (MIME),
Part One: Format of Internet Message Bodies
There are no IPv4 dependencies in this specification.
4.9. RFC 2046: MIME, Part Two: Media Types
There are no IPv4 dependencies in this specification.
4.10. RFC 2047: MIME, Part Three: Message Header Extensions
for Non-ASCII Text
There are no IPv4 dependencies in this specification.
4.11. RFC 2049: MIME Part Five: Conformance Criteria and
Examples
There are no IPv4 dependencies in this specification.
4.12. RFC 2279: UTF-8, a transformation format of ISO 10646
There are no IPv4 dependencies in this specification.
4.13. RFC 2347: TFTP Option Extension
There are no IPv4 dependencies in this specification.
Sofia & Nesser II Informational [Page 7]
4.14. RFC 2348: TFTP Blocksize Option
Section "Blocksize Option Specification" gives the following example: "For example:
+-------+--------+---+--------+---+--------+---+--------+---+
| 1 | foobar | 0 | octet | 0 | blksize| 0 | 1428 | 0 |
+-------+--------+---+--------+---+--------+---+--------+---+
is a Read Request, for the file named "foobar", in octet (binary) transfer mode, with a block size of 1428 octets (Ethernet MTU,
less the TFTP, UDP and IP header lengths)."
Clearly, the given blocksize example would not work with IPv6 header sizes, but it has no practical implications, since larger blocksizes are also available.
4.1
5. RFC 2349: TFTP Timeout Interval and Transfer Size Options
There are no IPv4 dependencies in this specification.
4.16. RFC 2355: TN3270 Enhancements
There are no IPv4 dependencies in this specification.
4.17. RFC 2396: Uniform Resource Identifiers (URI): Generic
Syntax
Section 3.2.2. (Server-based Naming Authority) states:
"The host is a domain name of a network host, or its IPv4 address as a set of four decimal digit groups separated by ".". Literal
IPv6 addresses are not supported.
...
Note: A suitable representation for including a literal IPv6
address as the host part of a URL is desired, but has not yet been determined or implemented in practice."
4.18. RFC 2616: Hypertext Transfer Protocol HTTP/1.1
Section 3.2.2 (http URL) states:
"The "http" scheme is used to locate network resources via the
HTTP protocol. This section defines the scheme-specific syntax
and semantics for http URLs.
http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]] Sofia & Nesser II Informational [Page 8]
If the port is empty or not given, port 80 is assumed. The
semantics are that the identified resource is located at the
server listening for TCP connections on that port of that host,
and the Request-URI for the resource is abs_path (section 5.1.2). The use of IP addresses in URLs SHOULD be avoided whenever
possible (see RFC 1900 [24])."
The text is version neutral, but it is unclear whether individual
implementations will support IPv6 addresses. In fact, the use of the ":"separator in IPv6 addresses will cause misinterpretation when
parsing URI’s. There are other discussions regarding a server
recognizing its own IP addresses, spoofing DNS/IP address
combinations, as well as issues regarding multiple HTTP servers
running on a single IP interface. Again, the text is version
neutral, but clearly, such statements represent implementation
issues.
4.19. RFC 3191: Minimal GSTN address format in Internet Mail
There are no IPv4 dependencies in this specification.
4.20. RFC 3192: Minimal FAX address format in Internet Mail
There are no IPv4 dependencies in this specification.
4.21. RFC 3282: Content Language Headers
There are no IPv4 dependencies in this specification.
4.22. RFC 3461: Simple Mail Transfer Protocol (SMTP) Service
Extension for Delivery Status Notifications
There are no IPv4 dependencies in this specification.
4.23. RFC 3462: The Multipart/Report Content Type for the
Reporting of Mail System Administrative Messages
There are no IPv4 dependencies in this specification.
4.24. RFC 3463: Enhanced Mail System Status Codes
There are no IPv4 dependencies in this specification.
4.2
5. RFC 3464: An Extensible Message Format for Delivery Status
Notifications
There are no IPv4 dependencies in this specification.
Sofia & Nesser II Informational [Page 9]
5. Proposed Standards
Proposed Standards represent initial level documents in the IETF
standards track process. They are stable in terms of design, but do not require the existence of implementations. In several cases,
these specifications are simply proposed as solid technical ideas, to be analysed by the Internet community, but are never implemented or
advanced in the IETF standards process.
5.1. RFC 698: Telnet extended ASCII option
There are no IPv4 dependencies in this specification.
5.2. RFC 726: Remote Controlled Transmission and Echoing Telnet
option
There are no IPv4 dependencies in this specification.
5.3. RFC 727: Telnet logout option
There are no IPv4 dependencies in this specification.
5.4. RFC 735: Revised Telnet byte macro option
There are no IPv4 dependencies in this specification.
5.5. RFC 736: Telnet SUPDUP option
There are no IPv4 dependencies in this specification.
5.6. RFC 749: Telnet SUPDUP-Output option
There are no IPv4 dependencies in this specification.
5.7. RFC 779: Telnet send-location option
There are no IPv4 dependencies in this specification.
5.8. RFC 885: Telnet end of record option
There are no IPv4 dependencies in this specification.
5.9. RFC 927: TACACS user identification Telnet option
There are no IPv4 dependencies in this specification.
Sofia & Nesser II Informational [Page 10]
5.10. RFC 933: Output marking Telnet option
There are no IPv4 dependencies in this specification.
5.11. RFC 946: Telnet terminal location number option
Section "TTYLOC Number" states:
"The TTYLOC number is a 64-bit number composed of two (2) 32-bit
numbers: The 32-bit official ARPA Internet host address (may be
any one of the addresses for multi-homed hosts) and a 32-bit
number representing the terminal on the specified host. The host address of [0.0.0.0] is defined to be "unknown", the terminal
number of FFFFFFFF (hex, r or-1 in decimal) is defined to be
"unknown" and the terminal number of FFFFFFFE (hex, or -2 in
decimal) is defined to be "detached" for processes that are not
attached to a terminal."
The clear reference to 32-bit numbers, and to the use of literal
addresses in the form [0.0.0.0] is clearly an IPv4-dependency. Thus, the text above needs to be re-written.
5.12. RFC 977: Network News Transfer Protocol
There are no IPv4 dependencies in this specification.
5.13. RFC 1041: Telnet 3270 regime option
There are no IPv4 dependencies in this specification.
5.14. RFC 1043: Telnet Data Entry Terminal option: DODIIS
implementation
There are no IPv4 dependencies in this specification.
5.15. RFC 1053: Telnet X.3 PAD option
There are no IPv4 dependencies in this specification.
5.1
6. RFC 1073: Telnet window size option
There are no IPv4 dependencies in this specification.
5.17. RFC 1079: Telnet terminal speed option
There are no IPv4 dependencies in this specification.
Sofia & Nesser II Informational [Page 11]
5.18. RFC 1091: Telnet terminal-type option
There are no IPv4 dependencies in this specification.
5.19. RFC 1096: Telnet X display location option
There are no IPv4 dependencies in this specification.
5.20. RFC 1274: The COSINE and Internet X.500 Schema
There are no IPv4 dependencies in this specification.
5.21. RFC 1276: Replication and Distributed Operations extensions
to provide an Internet Directory using X.500
There are no IPv4 dependencies in this specification.
5.22. RFC 1314: A File Format for the Exchange of Images in the
Internet
There are no IPv4 dependencies in this specification.
5.23. RFC 1328: X.400 1988 to 1984 downgrading
There are no IPv4 dependencies in this specification.
5.24. RFC 1372: Telnet Remote Flow Control Option
There are no IPv4 dependencies in this specification.
5.25. RFC 1415: FTP-FTAM Gateway Specification
Since this document defines a gateway for interaction between FTAM
and FTP, the only possible IPv4 dependencies are associated with FTP, which has already been investigated above, in section 3.16.
5.2
6. RFC 1494: Equivalences between 1988 X.400 and RFC-822
Message Bodies
There are no IPv4 dependencies in this specification.
5.27. RFC 1496: Rules for downgrading messages from X.400/88 to
X.400/84 when MIME content-types are present in the messages
There are no IPv4 dependencies in this specification.
Sofia & Nesser II Informational [Page 12]
5.28. RFC 1502: X.400 Use of Extended Character Sets
There are no IPv4 dependencies in this specification.
5.29. RFC 1572: Telnet Environment Option
There are no IPv4 dependencies in this specification.
5.30. RFC 1648: Postmaster Convention for X.400 Operations
There are no IPv4 dependencies in this specification.
5.31. RFC 1738: Uniform Resource Locators
Section 3.1. (Common Internet Scheme Syntax) states:
"host
The fully qualified domain name of a network host, or its IP
address as a set of four decimal digit groups separated by ".". Fully qualified domain names take the form as described in
Section 3.5 of RFC 1034 [13] and Section 2.1 of RFC 1123 [4]: a sequence of domain labels separated by ".", each domain label
starting and ending with an alphanumerical character and
possibly also containing "-" characters. The rightmost domain label will never start with a digit, though, which
syntactically distinguishes all domain names from the IP
addresses."
Clearly, this is only valid when using IPv4 addresses. Later in
Section 5. (BNF for specific URL schemes), there is the following
text:
"; URL schemeparts for ip based protocols:
ip-schemepart = "//" login [ "/" urlpath ]
login = [ user [ ":" password ] "@" ] hostport
hostport = host [ ":" port ]
host = hostname | hostnumber"
Again, this also has implications in terms of IP-version neutrality.
5.32. RFC 1740: MIME Encapsulation of Macintosh Files -
MacMIME
There are no IPv4 dependencies in this specification.
Sofia & Nesser II Informational [Page 13]
5.33. RFC 1767: MIME Encapsulation of EDI Objects
There are no IPv4 dependencies in this specification.
5.34. RFC 1808: Relative Uniform Resource Locators
There are no IPv4 dependencies in this specification.
5.35. RFC 1835: Architecture of the WHOIS++ service
There are no IPv4 dependencies in this specification.
5.3
6. RFC 1913: Architecture of the WHOIS++ Index Service
Section 6.5. (Query referral) makes the following statement:
"When referrals are included in the body of a response to a query, each referral is listed in a separate SERVER-TO-ASK block as shown below.
# SERVER-TO-ASK
Version-number: // version number of index software, used to insure
// compatibility
Body-of-Query: // the original query goes here
Server-Handle: // WHOIS++ handle of the referred server
Host-Name: // DNS name or IP address of the referred server
Port-Number: // Port number to which to connect, if different from the // WHOIS++ port number"
The syntax used does not present specific IPv4 dependencies, but
implementations should be modified to check, in incoming packets,
which IP version was used by the original request, so they can
determine whether or not to return an IPv6 address.
5.37. RFC 1914: How to Interact with a Whois++ Mesh
Section 4 (Caching) states the following:
"A client can cache all information it gets from a server for some time. For example records, IP-addresses of Whois++ servers, the
Directory of Services server etc.
A client can itself choose for how long it should cache the
information.
The IP-address of the Directory of Services server might not
change for a day or two, and neither might any other information." Sofia & Nesser II Informational [Page 14]
Also, subsection 4.1. (Caching a Whois++ servers hostname) contains: "An example of cached information that might change is the cached hostname, IP-address and portnumber which a client gets back in a servers-to-ask response. That information is cached in the server since the last poll, which might occurred several weeks ago.
Therefore, when such a connection fails, the client should fall
back to use the serverhandle instead, which means that it contacts the Directory of Services server and queries for a server with
that serverhandle. By doing this, the client should always get
the last known hostname.
An algorithm for this might be:
response := servers-to-ask response from server A
IP-address := find ip-address for response.hostname in DNS
connect to ip-address at port response.portnumber
if connection fails {
connect to Directory of Services server
query for host with serverhandle response.serverhandle
response := response from Directory of Services server
IP-address := find ip-address for response.hostname in DNS
connect to ip-address at port response.portnumber
if connection fails {
exit with error message
}
}
Query this new server"
The paragraph does not contain IPv4 specific syntax. Hence, IPv6
compliance will be implementation dependent.
5.38. RFC 1985: SMTP Service Extension for Remote Message
Queue Starting
There are no IPv4 dependencies in this specification.
5.39. RFC 2017: Definition of the URL MIME External-Body
Access-Type
There are no IPv4 dependencies in this specification.
5.40. RFC 2034: SMTP Service Extension for Returning Enhanced
Error Codes
There are no IPv4 dependencies in this specification.
Sofia & Nesser II Informational [Page 15]
5.41. RFC 2056: Uniform Resource Locators for Z39.50
There are no IPv4 dependencies in this specification.
5.42. RFC 2077: The Model Primary Content Type for
Multipurpose Internet Mail Extensions
There are no IPv4 dependencies in this specification.
5.43. RFC 2079: Definition of an X.500 Attribute Type and an
Object Class to Hold Uniform Resource Identifiers (URIs)
There are no IPv4 dependencies in this specification.
5.44. RFC 2086: IMAP4 ACL extension
There are no IPv4 dependencies in this specification.
5.45. RFC 2087: IMAP4 QUOTA extension
There are no IPv4 dependencies in this specification.
5.4
6. RFC 2088: IMAP4 non-synchronizing literals
There are no IPv4 dependencies in this specification.
5.47. RFC 2122: VEMMI URL Specification
Section 3 (Description of the VEMMI scheme) states:
"The VEMMI URL scheme is used to designate multimedia interactive services conforming to the VEMMI standard (ITU/T T.107 and ETS 300 709).
A VEMMI URL takes the form:
vemmi://
as specified in Section 3.1. of RFC 1738. If :
IPv4 dependencies may relate to the possibility of the
Sofia & Nesser II Informational [Page 16]
5.48. RFC 2141: URN Syntax
There are no IPv4 dependencies in this specification.
5.49. RFC 2142: Mailbox Names for Common Services, Roles and
Functions
There are no IPv4 dependencies in this specification.
5.50. RFC 2156: MIXER (Mime Internet X.400 Enhanced Relay):
Mapping between X.400 and RFC 822/MIME
There are no IPv4 dependencies in this specification.
5.51. RFC 2157: Mapping between X.400 and RFC-822/MIME
Message Bodies
There are no IPv4 dependencies in this specification.
5.52. RFC 2158: X.400 Image Body Parts
There are no IPv4 dependencies in this specification.
5.53. RFC 2159: A MIME Body Part for FAX
There are no IPv4 dependencies in this specification.
5.54. RFC 2160: Carrying PostScript in X.400 and MIME
There are no IPv4 dependencies in this specification.
5.55. RFC 2163: Using the Internet DNS to Distribute MIXER
Conformant Global Address Mapping
There are no IPv4 dependencies in this specification.
5.5
6. RFC 2164: Use of an X.500/LDAP directory to support
MIXER address mapping
There are no IPv4 dependencies in this specification.
5.57. RFC 2165: Service Location Protocol
Section 7. (Service Type Request Message Format) and Section 9.
(Service Registration Message Format) have an 80-bit field from
addr-spec (see below) which cannot support IPv6 addresses. Also,
Section 20.1. (Previous Responders’ Address Specification) states: Sofia & Nesser II Informational [Page 17]
"The previous responders’ Address Specification is specified as
for Address Specifications in Service Location is defined in
section 20.4. The comma delimiter is required between each
Later, in Section 20.4. (Address Specification in Service Location)
there is also the following reference to addr-spec:
"The address specification used in Service Location is:
dotted decimal IP address notation
When no Domain Name Server is available, SAs and DAs must use
dotted decimal conventions for IP addresses. Otherwise, it is
preferable to use a fully qualified domain name wherever possible as renumbering of host addresses will make IP addresses invalid
over time."
The whole Section 21. (Protocol Requirements) defines the
requirements for each of the elements of this protocol. Several IPv4 statements are made, but the syntax used is sufficiently neutral to
apply to the use of IPv6.
Section 22. (Configurable Parameters and Default Values) states:
"There are several configuration parameters for Service Location. Default values are chosen to allow protocol operation without the need for selection of these configuration parameters, but other
values may be selected by the site administrator. The
configurable parameters will allow an implementation of Service
Location to be more useful in a variety of scenarios.
Sofia & Nesser II Informational [Page 18]
Multicast vs. Broadcast
All Service Location entities must use multicast by default. The ability to use broadcast messages must be configurable
for UAs and SAs. Broadcast messages are to be used in
environments where not all Service Location entities have
hardware or software which supports multicast.
Multicast Radius
Multicast requests should be sent to all subnets in a site. The default multicast radius for a site is 32. This value
must be configurable. The value for the site’s multicast
TTL may be obtained from DHCP using an option which is
currently unassigned."
Once again, nothing here precludes IPv6, Section 23.
(Non-configurable Parameters) states:
"IP Port number for unicast requests to Directory Agents:
UDP and TCP Port Number: 427
Multicast Addresses
Service Location General Multicast Address: 224.0.1.22 Directory Agent Discovery Multicast Address: 224.0.1.35
A range of 1024 contiguous multicast addresses for use as Service Specific Discovery Multicast Addresses will be assigned by IANA."
Clearly, the statements above require specifications related to the
use of IPv6 multicast addresses with equivalent functionality.
5.58. RFC 2177: IMAP4 IDLE command
There are no IPv4 dependencies in this specification.
5.59. RFC 2183: Communicating Presentation Information in
Internet Messages: The Content-Disposition Header Field
There are no IPv4 dependencies in this specification.
5.60. RFC 2192: IMAP URL Scheme
The specification has IPv4 dependencies, as RFC 1738, which is
integral to the document, is not IPv6 aware.
Sofia & Nesser II Informational [Page 19]
5.61. RFC 2193: IMAP4 Mailbox Referrals
Section 6. (Formal Syntax) presents the following statement:
"referral_response_code = "[" "REFERRAL" 1*(SPACE
The above presents dependencies on RFC 1738 URL definitions, which
have already been mentioned in this document, section 5.31.
5.62. RFC 2218: A Common Schema for the Internet White Pages
Service
There are no IPv4 dependencies in this specification.
5.63. RFC 2221: IMAP4 Login Referrals
Section 4.1. (LOGIN and AUTHENTICATE Referrals) provides the
following example:
"Example: C: A001 LOGIN MIKE PASSWORD
S: A001 NO [REFERRAL IMAP://MIKE@SERVER2/] Specified
user is invalid on this server. Try SERVER2."
Even though the syntax "user@SERVER2" is presented often, there are
no specifications related to the format of "SERVER2". Hence, it is
up to individual implementations to determine acceptable values for
the hostname. This may or not include explicit IPv6 addresses.
5.64. RFC 2227: Simple Hit-Metering and Usage-Limiting for
HTTP
There are no IPv4 dependencies in this specification.
5.65. RFC 2231: MIME Parameter Value and Encoded Word
Extensions: Character Sets, Languages, and Continuations
There are no IPv4 dependencies in this specification.
5.6
6. RFC 2234: Augmented BNF for Syntax Specifications: ABNF
There are no IPv4 dependencies in this specification.
5.67. RFC 2244: Application Configuration Access Protocol
There are no IPv4 dependencies in this specification.
Sofia & Nesser II Informational [Page 20]
短语结构类型 短语是由词和词按一定的方式组合而成的。它主要有五种类型：并列短语、偏正短语、主谓短语、动宾短语、后补短语。 并列短语 由两个或两个以上的名词、动词或形容词组合而成，词与词之间是并列关系，中间常用顿号或“和、及、又、与、并”等连词。 常见的结构形式有： 名词＋名词，如：文化教育今天或明天良师益友 动词＋动词，如：调查研究愿意并实行团结互助团结和谐 形容词＋形容词，如：光辉灿烂庄严肃穆万紫千红风和日丽 代词＋代词，如：我和他这样那样 数量词＋数量词，如：四面八方千秋万代半斤八两 并列短语一般前后可以互换位置，如：工厂、农村，我、你、他等。但有些并列短语是不能前后颠倒位置的，因为它有一定次序。如：春、夏、秋、冬（时间顺序），省、市、县（大小顺序），老、中、青（年龄顺序），继承和发展接近文学和爱好文学（逻辑顺序），男女老少金银铜铁油盐酱醋（语言习惯）等等。 偏正短语 由名词、动词或形容词与它们前面起修饰作用的词组合而成，即前面是修饰语，后面是中心语。 中心语是名词时，修饰限制成分是定语，用（）表示，常常用“的” 字连接。
常见的结构形式有： 形容词+名词,如：美丽的花朵伟大的人民浩瀚的大海 数量词+名词，如：一杯水一位顾客三斤水果 名词+名词，如：学校的图书馆祖国大地烟台的苹果 代词+名词，如：大家的心情我的老师自己的心情 中心语是动词或形容词时，修饰语是状语，用〔〕表示，常常有“地”字。 常见的结构形式有： 形容词+动词，如：慢慢地走激动地演讲迅速地回答 副词+动词，如：完全相信十分思念突然发现 副词+形容词，如：非常美丽更加坚决相当迅速 主谓短语 由被陈述与陈述的两部分组合而成。被陈述的部分是主语，可以回答谓语“谁”、“什么”，一般由名词、名词性短语、代词等充当；陈述的部分是谓语，可以回答主语“怎么样”，一般由动词、形容词、动词性短语、形容词性短语充当。 常见的结构形式有： 名词+动词，如：会议结束蝴蝶飞舞菊花开放 代词+动词，如：自己说话谁同意我们回去 名词+形容词，如：花朵鲜艳斗志昂扬阳光灿烂 代词+形容词，如：你真美丽这里清静大家激动 另外，还有特殊主谓短语，即名词做谓语。
短语的结构分类 短语按照结构来考察，可以分为十种：并列短语、偏正短语、动宾短语、介宾短语、补充短语、主谓短语、的字短语、兼语短语、连动短语、固定短语。 [口诀]短语看结构，十种莫忧愁。并偏动介补，主的兼连固。 1、并列短语 词语之间互不修饰限制，地位平等，这样的短语就是并列短语，也称为“联合短语”。 这类短语主要由名词、动词、形容词、代词、数量词这四种词语自我构成，或者几种词语搭配构成，主要有五种形式，可以简单表示为：名+名、形+形、动+动、代+代、数量+数量 例如：崇山峻岭柴米油盐思想感情民俗风情老师和同学国家与集体个人与社会 发展变化研究决定调查研究总结推广吃喝穿戴继承和发扬继承与创新 婉转悠扬和谐幸福金碧辉煌富丽堂皇庄严肃穆丰富而富饶光荣而艰巨 你、我、他你和我这门那户这个那个彼此彼此谁谁谁一个和八个 2、偏正短语 词语之间有修饰限制关系，前一个词语对后一个词语进行修饰和限制，而以后一个词语为中心，词语与词语之间是偏正关系，这样的短语是偏正短语。修饰名词的词叫定语，用（）来表示；修饰动词、形容词的词叫状语，用〔〕来表示。这类短语主要以名词、动词、形容词为主体构成，主要有三种形式，简单记为：形.+ 名/副.+动./副.+形.，例如：（1）名词性偏正短语——定语+名词（或代词） ①名词、代词、动词、形容词作定语。例如： 名+名：中华情赤壁赋出师表兰亭集序荷塘月色故都的秋赤壁之战 代+名：我们家这个人之二虫这只黄鹂那只白鹭这条纱巾那根拐棍 动+名：发言稿止痛片美发厅调查提纲训练计划运动规律游览路线 形+名：黑牡丹红太阳白玫瑰绿色食品经典作品优秀分子永恒魅力 ②指示代词、数词、量词组合作定语。 例如：（指+数+量）+名：这支笔这一位委员那一个书包这两个人那一年六月 （数+量）+名：七根火柴一年四季一件小事一曲窦娥冤千古关汉卿 （2）动词性偏正短语——状语+动词 ①状语表示的意义 状语可以表示动作、行为的情态、时间、频率、围、处所、对象等。例如： 表示情态：努力进取认真研究大力发展倾情奉献喜闻乐见娓娓动听 表示时间：猝死马上出发立刻行动现在开始从眼前抓起于拂晓结束 表示频率：间进经常说寻常见几度闻一再强调再三叮嘱常来常往
感官动词和使役动词 默认分类2010-05-28 23:14:26 阅读46 评论0 字号：大中小订阅 使役动词，比如let make have就是3个比较重要的 have sb to do 没有这个用法的 只有have sb doing.听凭某人做某事 have sb do 让某人做某事 have sth done 让某事被完成（就是让别人做） 另外： 使役动词 1.使役动词是表示使、令、让、帮、叫等意义的不完全及物动词,主要有make(使,令), let(让), help(帮助), have(叫)等。 2.使役动词后接受词,再接原形不定词作受词补语。 He made me laugh. 他使我发笑。 I let him go. 我让他走开。 I helped him repair the car. 我帮他修理汽车。 Please have him come here. 请叫他到这里来。 3.使役动词还可以接过去分词作受词补语。 I have my hair cut every month. 我每个月理发。 4.使役动词的被动语态的受词补语用不定词,不用原形不定词。 (主)He made me laugh. 他使我笑了。 (被)I was made to laugh by him. 我被他逗笑了。 使役动词有以下用法： a. have somebody do sth让某人去做某事 ??i had him arrange for a car. b. have somebody doing sth.让某人持续做某事。 ??he had us laughing all through lunch. 注意：用于否定名时，表示“允许” i won't have you running around in the house. 我不允许你在家里到处乱跑。 ******** 小议“使役动词”的用法 1. have sb do 让某人干某事 e.g:What would you have me do? have sb/sth doing 让某人或某事处于某种状态，听任 e.g: I won't have women working in our company. The two cheats had the light burning all night long. have sth done 让别人干某事，遭受到 e.g:you 'd better have your teeth pulled out. He had his pocket picked. notes: "done"这个动作不是主语发出来的。 2.make sb do sth 让某人干某事 e.g:They made me repeat the story. What makes the grass grow?
第一节短语结构与句子成分 （一）教学目标： 1、理解偏正短语和并列短语的区别以及偏正短语的类型； 2、理解句子的六种成分以及各成分在句中的作用。 3、能够熟练辨析短语结构、熟练分析句子成分。 （二）教学重点： 以上目标均为重点。 （三）教学难点： 1、区别句短语和句子； 2、理解介宾短语； 3、区别宾语和补语。 （四）教学步骤： 1、短语结构。 （1）短语的概念：短语是词的组合，是意义和语法上能搭配而没有句调的一组词，所以又叫词组。短语是比词大比句小的语言单位。 （2）短语的结构类型： 按结构分类，即短语的结构类。 ①主谓短语：粮食丰收春草吐青阳光灿烂明天星期三 ②动宾短语：想妈妈盖被子接受批评经受考验喜欢清净 偏正短语： ③定中短语： 江苏人（代+名）昨天的事（名+名）前进的步伐（动+名）新书（形+名）野生动物（形+名）十吨钢材（数量+名） 经济的逐步发展（名+动）他们的估计（代+动）美妙的渲染（形+动）求学的迫切希望（动+动）灯火的辉煌（名+形）别人的精明（代+形）（分析的精确（动+形）说不出的高兴（动+形） ④状中短语：马上回来（副+动）今天出发（名+动）花园里谈（方位短语+动）这么走（代+动）绕道走（动+动）慢走（形+动）一步一步走（数量+动）吱吱地叫（拟声+动）为人民服务（介宾+动）非常宽（副+形）这么宽（代+形）三尺宽（数量+形） ⑤中补短语：打死（动+动）学得好（动+形）看了一次（动+数量）走到天涯海角（动+介宾）高兴极了（动+副） ⑥联合短语：勤学好问深思熟虑今天和明天来不来又大又圆伟大而质朴既准确又形象升学或者就业一个或两个（构成短语的两个部分是并列关系） ⑦介词短语：（用大腕）盛汤（比前几年）好得多（为了健康）而锻炼（被巨浪）撕成碎片（向英雄模范）学习（关于嫦娥奔月）的神话（针对核心问题）发言（通过这种方式）表达不满 ⑧另外还有连谓短语，如“出去闲逛”、“听了高兴”；兼语短语，如“请他进来”、“通知各单位来开会”；同位短语，如“首都北京”、“我们大家”；方位短语，如“大门外”、“操场上”；量词短语，如“一打”、“两瓶”；助词短语，如“大的”、“吃的”、“暴风雨般”、“触电一样”、“所想”、“所需要”。 （3）短语的其它分类标准：（了解）
短语结构类型 1、定义：由若干词构成的造句单位。 2、常见的短语类型： 一、并列短语 词和词之间没有轻重主次之分，彼此地位平等。 １、类型 ⑴名＋名文化教育今天或明天（名词短语） ⑵动＋动调查研究愿意并实行（动词短语） ⑶形＋形光辉灿烂庄严肃穆（形容词短语） ⑷代＋代我和他这样那样（名词短语） ⑸数量＋数量四面八方千秋万代三斤五两（名词短语） ２、并列短语一般前后可以互换位置。 例如：工厂农村我你他 但有些并列短语是不能前后颠倒位置的，因为它有一定次序。 ⑴时间顺序：春、夏、秋、冬 ⑵大小顺序：省、市、县 ⑶年龄顺序：老、中、青 ⑷逻辑顺序：继承和发展接近文学和爱好文学 ⑸语言习惯：男女老少金银铜铁油盐酱醋 ３、并列短语一般要求词性相同，但个别也有不同。 例如：姐姐和我（名词＋代词）勤劳勇敢不怕苦（形＋形＋代） 二、偏正短语 １、前偏后正：“偏”修饰、限制“正”。 ⑴定＋中（名、代），如：（祖国）大地（一朵）茶花（前进）的步伐 ⑵状＋中（动、形），如：[很]好看[独立]思考[慢慢]地走 ２、旧语法：“的”是定语的标志；“地”是状语的标志。新语法：统一为“的”。 三、动宾短语
动宾之间是支配与被支配、关涉与被关涉的关系。动词＋宾语。宾语是回答动词“谁”、“什么”、“哪儿”的。例如：消灭敌人放下包袱丢下它发展生产进行斗争骗取信任恢复平静爱热闹下决心有幽默感像珍珠 四、补充短语 A、动+补 动补短语中的补语不能回答动词“谁”、“什么”“哪儿”。 例如： 看清楚、去一趟、拿起来、引在脑子里、跑得快、走的急 B、形+补 以形容词为中心时它的后面只有补语，因为形容词不能带宾语。 结构助词“得”是补语的标志。 例如：机灵得很密得不透气漂亮极了 五、主谓短语 陈述与被陈述的关系。名词（代词）+动词（形容词） 主语可以回答谓语“谁”、“什么”；谓语可以回答主语“怎么样” 结构形式：A名+动B名+形C代+动D代+形 例如：觉悟提高思想解放阳光灿烂心情舒畅 特殊主谓短语：名词做谓语。例如：今天星期三明天国庆节他中等身材 判断短语类型的窍门 短语是由词和词构成的，短语可以作为句子成分；大多数短语加上一定的语调就可以成为句子。 词和词构成短语，形成一定的结构关系和短语成分： 1．并列短语：由两个或两个以上的名词、动词或形容词并列组成，词和词之间是平等的联合，没有轻重主次之分。 例如：报纸杂志、老师和同学、雄伟壮丽、唱歌又跳舞、调查研究、光荣而艰巨 2．偏正短语：由名词、动词或形容词和在它们前头起修饰限制作用的词组成。其中名词、动词或形容词是中心语，修饰句词的词语是定语，修饰动词、形容词的词语是状语。定语、状语与中心语的关系，是偏和正的关系。定语用“( )”表示，状语用“［］”表示，中心语不标符号。 例如：(汉语)语法、(祖国)大地 ［完全］相信、［小心］翻阅、［更加］坚强、［多么］伟大 3．动宾短语：由动词和它的宾语组成。宾语在动词之后，是动词的支配成分，表示动作行为的对象、结果、处所等。 例如：吃晚饭、盖房子、住石洞 有的动词(如“给、送、教、告诉”等)可以带两个宾语。这样的宾语叫双宾语。离动词近的叫近宾语，离动词远的叫远宾语。 例如：给我笔、教你一首歌 4．补充短语：由动词或形容词和补语组成。补语在动词或形容词之后，对动词或形容词起补充说明的作用。建议将动词、形容词和补语组成的短语称补充短语。这样，补充短语分为两类，一是动补短语，一是形补短语。补语用“〈〉”表示。 例如：洗得〈干净〉、翻了〈一阵〉、抱〈起来〉、活跃〈在基层〉、热得〈出汗〉、大得〈多〉 5．主谓短语：由主语和谓语组成。主语在前，表示陈述对象；谓语在后，表示陈述的内容。 例如：红旗飘扬天气好
关于短语的语法 一、并列短语 词和词之间没有轻重主次之分，彼此地位平等。 1、类型 ⑴名＋名文化教育今天或明天（名词短语） ⑵动＋动调查研究愿意并实行（动词短语） ⑶形＋形光辉灿烂庄严肃穆（形容词短语） ⑷代＋代我和他这样那样（名词短语） ⑸数量＋数量四面八方千秋万代三斤五两（名词短语） 2、并列短语一般前后可以互换位置。 但有些并列短语是不能前后颠倒位置的，因为它有一定次序。 ⑴时间顺序：春、夏、秋、冬 ⑵大小顺序：省、市、县 ⑶年龄顺序：老、中、青 ⑷逻辑顺序：继承和发展接近文学和爱好文学 ⑸语言习惯：男女老少金银铜铁油盐酱醋 二、偏正短语 前偏后正：“偏”修饰、限制“正”。 ⑴定＋中（名、代），如：（祖国）大地（一朵）茶花（前进）的步伐 ⑵状＋中（动、形），如：[很]好看[独立]思考[慢慢]地走 三、动宾短语 动宾之间是支配与被支配、关涉与被关涉的关系。动词＋宾语。宾语是回答动词“谁”、“什么”、“哪儿”的。 例如：消灭敌人放下包袱丢下它发展生产进行斗争、 骗取信任恢复平静爱热闹下决心有幽默感像珍珠 四、动补短语 动词+补语 动补短语中的补语是用来修饰动词的 例如： 看清楚、去一趟、拿起来、引在脑子里 五、形补短语 形容词+补语 以形容词为中心时它的后面只有补语，因为形容词不能带宾语。 结构助词“得”是补语的标志。 例如： 跑得快走得急机灵得很密得不透气 六、主谓短语 陈述与被陈述的关系。名词（代词）+动词（形容词） 主语可以回答谓语“谁”、“什么”；谓语可以回答主语“怎么样” 例如： 觉悟提高思想解放阳光灿烂心情舒畅 特殊主谓短语：名词做谓语。 例如：
今天星期三明天国庆节他中等身材 七、量词短语 由数词或指示代词加上量词组成。 1、数量短语：一个、二斤、四里、三次、一回、三只、一碗、两包 2、指量短语：这种、那种、这堆、这次、那回。 八、介宾短语 由介词加上后面的名词、代词或名词短语组成。 介加名、介加代、介加名词短语 例如： 为人民（服务）对群众（说）从现在（起）关于课堂纪律问题当黎明到来的时候按规定（办理）把大门（推开）
感官动词 1.see, hear, listen to, watch, notice等词，后接宾语，再接省略to的动词不定式或ing形式。前者表全过程，后者表正在进行。句中有频率词时，以上的词也常跟动词原形。 注释:省略to的动词不定式--to do是动词不定式，省略了to,剩下do，其形式和动词原形是一样的，但说法不同。 see sb do sth 看到某人做了某事 see sb doing sth 看到某人在做某事 hear sb do sth 听到某人做了某事 hear sb doing sth 听到某人在做某事 以此类推... I heard someone knocking at the door when I fell asleep. (我入睡时有人正敲门,强调当时正在敲门) I heard someone knock at the door three times. (听到有人敲门的全过程) I often watch my classmates play volleyball after school. (此处有频率词often) （了解）若以上词用于被动语态，须将省略的to还原： see sb do sth----sb be seen to do sth hear sb do sth----sb be seen to do sth 以此类推... We saw him go into the restaurant. → He was seen to go into the restaurant. I hear the boy cry every day. → The boy is heard to cry every day. 2.感官动词look, sound, smell, taste, feel可当系动词，后接形容词。 He looks angry. His explanation sounds reasonable. The cakes smell nice.
短语结构类型 一、指出下列短语的结构 1．风俗习惯( ) 2.变化规律( ) 3.历史悠久( ) 4.整修一新( ) 5.交头接耳( ) 6.思维敏捷( )7.废寝忘食( ) 8.前程远大( ) 9.全神贯注( ) 10.襟怀坦白( ) 11.挥手之间( ) 12.愚公移山( ) 13.竞选州长( ) 14.销售计划( ) 15.色彩缤纷( )16.交通规则( ) 17.风和日丽( ) 18.激动不已( )19.禁止吸烟( ) 20.辛勤耕耘( ) 21.巍峨挺立( )22.不断发生( ) 23.气氛热烈( ) 24.继往开来 ( ) 二、下列各组短语分别以哪组类型短语为主，其中不同的短语各是哪个，属于什么类型短语。 1.A.祖国万岁 B.品质优良 C.天气晴和 D.思想品质 E.成绩好 2.A.看了两眼 B.打扫教室 C.洗得干净 D.热了起来 E.扔出去 3.A.十分伟大 B.我的书包 C.小声地说 D.追歼敌人 E.很热闹 4.A.讲解语法 B.讲述清楚 C.种植玉米 D.制造火箭 E.听故事 5.A.用圆珠笔(写)B.对于我们 C.按照习惯 D.必然产生 E.被大雨(淋) 6.A.报纸杂志 B.调查研究 C.身体健康 D.严肃认真 E.读和写 三、辨别下列课文题目的结构类型 1.济南的冬天 2.纪念白求恩３.蚊子和狮子 4.死海不死 5.事事关心 6.反对自由主义 7.中国石拱桥 8.白杨礼赞 9.皇帝的新装 10.同志的信任 11.《论语》十则 12.老杨同志 13.向沙漠进军14.记一辆纺车 15.批评和自我批评 16.谈骨气 17.最后一课18.在烈日和暴雨下19.忆江南 20.桃花源记 21.想和做22.说谦虚 四、指出下列画横线的短语的结构类型： 1、早听说香山红叶是北京最浓最浓的秋色，能去看看，自然乐意。我去的那日，天也作美，明净高爽，好得不能再好了；人也奏巧，居然找到了一位老向导。这位老向导就住在西山脚下，早年做过四十年的向导，胡子都白了，还是腰板挺直，硬朗得很。 2、从大会堂北门进去，穿过大理石柱廊、风门厅、衣帽厅，就进入宴会厅底层大厅。 3、黄显声的报纸每天按时送还，铅笔、薄纸和刀片都妥善地收藏起来。 4、调皮的人们围上来，七嘴八舌打趣他。 5、发动机、卷扬机、混凝土搅拌机和空气压缩机的吼声，震荡山谷。 6、小时候有一回上树掐海棠花，不想叫蜜蜂蜇了一下，痛得我差点儿跌下来。 五、按照下列要求各写出三个短语来，并指出它们的结构类型： 1.定语+ 中心词 2.状语+ 中心词 3.中心词+ 补语 4.谓语+ 宾语 5.主语+ 谓语 六、指出下列短语变换内部次序前后的结构类型： 政治学习责任重大达到目的 学习政治重大责任目的达到 津津有味地品尝认真地学习吃饭的时候 品尝得津津有味认真的态度吃得真快 七、选出正确答案 1．下列词语中,与“卧薪尝胆”结构完全相同的一项是（） A．偃旗息鼓惩前毖后温故知新巧妙绝伦 B．尊师重教惟妙惟肖赴汤蹈火心旷神怡C．趋吉避凶理屈词穷潜滋暗长随机应变 D．走马观花饮水思源扬眉吐气粉身碎骨2．选出下列短语在结构分类正确的一项（） ①山川大地②声音响亮③经济特区④渐渐消散 ⑤顾全大局⑥雄伟壮丽⑦结构坚固⑧竞选州长 A．①③/ ②⑥⑦/ ④⑤⑧ B．①③⑥/ ②⑦/ ④⑧/ ⑤ C．①⑥/ ②④⑦/ ③⑤/ ⑧ D．①⑥/ ②⑦/ ③④/ ⑤⑧ 3．全是主谓短语的一项是（） A．亚洲西部前功尽弃种类繁多 B．知识贫乏经验不足参加会议 C．起草方案朝晖夕阴洗得干净 D．工作繁忙须发花白意志坚强 4．短语结构类型不相同的一项是（） A．我的老师人类的语言济南的冬天 B．竞选州长记一辆纺车纪念白求恩C．蚊子和狮子怀疑与学习想和做 D．范进中举曹刿论战最后一课 5．下列课文标题都是偏正短语的一组是（）
《短语类型结构》教学设计 一、教学目标 1、理解短语的五种结构类型。 2、理解五种短语类型的概念及结构层次关系。 3、能正确划分短语的种类。 4、培养学生热爱祖国语言文字的兴趣，增强学生对母语的情感。 二、教学重点：根据所学概念，正确划分短语类型。， 三、教学难点：短语的概念及结构层次关系。 四、教学方法： 1、先掌短语结构的分类。即主谓短语、偏正短语、动宾短语、后补短语、并列短语等五种。 2、用多媒体依次演示各类短语的概念和例子，目的是让学生掌握每一类短语的结构特点及能用实例解答抽象的概念。 3、学生能自己举实例巩固学过的知识。 五、教学过程： （一）、导课 （二）、新课教学 1、并列短语：并列短语是由两个或两个以上的名词，动词或形容词并列组成的短语。词和词之间是平等的联合，没有轻重主次之分。（判断技巧：在短语的两个成分之间加上“和”“又”“并”“及”等表并列的连词，语意不变） 例如：（多媒体展示） 花草树木珠光宝气改革开放唱歌和跳舞团结互助雄伟壮丽讨论通过继承和发展聪明美丽光辉灿烂庄严肃穆万紫千红 学生举例（略） 2、偏正短语：偏正短语是由名词、动词或形容词与它们前头的起修饰作用的成分组成短语，其中名词、动词、形容词是中心语，修饰名词的成分是定语，修饰动词、形容词的成分是状语。定语、状语与中心语的关系，是偏和正的关系。（判断技巧：在短语两个成分之间加上结构助词“的”或“地”语意不变） 例如：（多媒体展示） 我的老师恭敬地鞠躬小心观察世外桃源突然发现 清晰的字迹小心地翻阅一个顾客完全相信 学生举例（略） 3、主谓短语：主谓短语是由两个表示被陈述与陈述关系的的词组成的短语，其中表示被陈述的对象是主语，用来陈述的是谓语。主语一般由名词，代词充当，谓语一般由动词、形容词充当。（判断技巧：在短语两个成分之间加上副词“很”“就”“都”等，语意不变） 例如：（多媒体展示）： 老师讲课阳光灿烂精力充沛觉悟提高思想解放阳光灿烂心情舒畅通俗易懂我们学习斗志昂扬意志坚定身心愉悦 学生举例（略）
八年级短语类型及试题 一、短语类型 偏正短语:前偏后正，“偏”修饰，限制“正”。 鉴别词： 常见的结构形式有： 形容词+名词,如：美丽的花朵伟大的人民浩瀚的大海 数量词+名词，如：一杯水一位顾客三斤水果 名词+名词，如：学校的图书馆祖国大地烟台的苹果 代词+名词，如：大家的心情我的老师自己的心情 中心语是动词或形容词时，修饰语是状语，用〔〕表示，常常有“地”字。 常见的结构形式有： 形容词+动词，如：慢慢地走激动地演讲迅速地回答 副词+动词，如：完全相信十分思念突然发现 副词+形容词，如：非常美丽更加坚决相当迅速 动宾短语:动宾之间是支配与被支配，干涉与被干涉的关系。动词+宾语。宾语是回答动词“谁”、“什么”、“哪”的。 鉴别词：着；了；过 常见的结构形式有： 动词+名词，如：敬畏生命热爱工作上中学 动词+代词，如：丢掉它们关爱自己想念大家 主谓短语:结构内部两个成分之间有陈述和被陈述之间的关系。 鉴别词：已经；很 常见的结构形式有： 名词+动词，如：会议结束蝴蝶飞舞菊花开放 代词+动词，如：自己说话谁同意我们回去 名词+形容词，如：花朵鲜艳斗志昂扬阳光灿烂 代词+形容词，如：你真美丽这里清静大家激动
另外，还有特殊主谓短语，即名词做谓语。 如：今天星期三明天国庆节他中等身材你是中学生 并列短语:词和词之间没有轻重主次之分，彼此地位平等。 鉴别词：和、而、或 常见的结构形式有： 名词＋名词，如：文化教育今天或明天良师益友 动词＋动词，如：调查研究愿意并实行团结互助团结和谐 形容词＋形容词，如：光辉灿烂庄严肃穆万紫千红风和日丽 代词＋代词，如：我和他这样那样 数量词＋数量词，如：四面八方千秋万代半斤八两 并列短语一般前后可以互换位置，如：工厂、农村，我、你、他等。但有些并列短语是不能前后颠倒位置的，因为它有一定次序。如：春、夏、秋、冬（时间顺序），省、市、县（大小顺序），老、中、青（年龄顺序），继承和发展接近文学和爱好文学（逻辑顺序），男女老少金银铜铁油盐酱醋（语言习惯）等等。 后补短语：结构内部两个成分之间有补充和被补充的关系。 鉴别词：得 常见的结构形式有： 动词+补语，如：写得好坐在石头上休息一会儿 形容词+补语，如：美丽极了密得不透气开心得一蹦三尺高 二、试题精讲 1、短语结构各不相同的一项是：（） Ａ、艰苦奋斗传播真理思想进步愚公移山 Ｂ、范进中举开沟挖渠认真学习取得成功 Ｃ、安邦定国跑向操场保护血管发表见解 Ｄ、打得惨败雨后彩虹崇高理想关系明确
英语中感官动词的用法 一、感官动词 1、感官动词(及物动词)有：see/notice/look at/watch/observe/listen to/hear/feel(Vt)/taste(Vt)/smell(Vt) 2、连缀动词(含感官不及物动词) be/get/become/feel/look/sound/smell/taste/keep/stay/seem/ appear/grow/turn/prove/remain/go/run 二、具体用法： 1、see, hear, smell, taste, feel,这五个动词均可作连系动词，后面接形容词作表语，说明主语所处的状态。其意思分别为"看/听/闻/尝/摸起来……"。除look之外，其它几个动词的主语往往是物，而不是人。 例如：These flowers smell very sweet.这些花闻起来很香。 The tomatoes feel very soft.这些西红柿摸起来很软。 2、这些动词后面也可接介词like短语，like后面常用名词。 例如：Her idea sounds like fun.她的主意听起来很有趣。 3、这五个感官动词也可作实义动词,除look(当"看起来……"讲时)只能作不及物动词外,其余四个既可作及物动词也可作不及物动词,此时作为实义动词讲时其主语一般为人。 例如:She smelt the meat.她闻了闻那块肉。 I felt in my pocket for cigarettes.我用手在口袋里摸香烟。 4、taste, smell作不及物动词时,可用于"t aste / smell + of +名词"结构,意为"有……味道/气味"。 例如:The air in the room smells of earth.房间里的空气有股泥土味。 5、它们(sound除外)可以直接作名词,与have或take构成短语。 例如：May I have a taste of the mooncakes?我可以尝一口这月饼吗？taste有品位、味道的意思。 例如：I don’t like the taste of the garlic.我不喜欢大蒜的味道。 She dresses in poor taste.她穿着没有品位。 look有外观，特色的意思，例：The place has a European look.此地具有欧洲特色。 feel有感觉，感受的意思，watch有手表，观察的意思。例：My watch is expensive.我的手表很贵。 6、其中look, sound, feel还能构成"look / sound / feel + as if +从句"结构，意为"看起来/听起来/感觉好像……"。 例如：It looks as if our class is going to win.看来我们班好像要获胜了。 7、感官动词+do与+doing的区别： see, watch, observe, notice, look at, hear, listen to, smell, taste, feel + do表示动作的完整性，真实性；+doing 表示动作的连续性，进行性。 I saw him work in the garden yesterday.昨天我看见他在花园里干活了。(强调"我看见了"
短语的结构 一、并列短语 词和词之间没有轻重主次之分，彼此地位平等。 １、类型 ⑴名＋名文化教育今天或明天（名词短语） ⑵动＋动调查研究愿意并实行（动词短语） ⑶形＋形光辉灿烂庄严肃穆（形容词短语） ⑷代＋代我和他这样那样（名词短语） ⑸数量＋数量四面八方千秋万代三斤五两（名词短语） ２、并列短语一般前后可以互换位置。 例如：工厂农村我你他 但有些并列短语是不能前后颠倒位置的，因为它有一定次序。 ⑴时间顺序：春、夏、秋、冬 ⑵大小顺序：省、市、县 ⑶年龄顺序：老、中、青 ⑷逻辑顺序：继承和发展接近文学和爱好文学 ⑸语言习惯：男女老少金银铜铁油盐酱醋 ３、并列短语一般要求词性相同，但个别也有不同。 例如：姐姐和我（名词＋代词）勤劳勇敢不怕苦（形＋形＋代） 二、偏正短语 １、前偏后正：“偏”修饰、限制“正”。 ⑴定＋中（名、代），如：（祖国）大地（一朵）茶花（前进）的步伐 ⑵状＋中（动、形），如：[很]好看[独立]思考[慢慢]地走 ２、旧语法：“的”是定语的标志；“地”是状语的标志。新语法：统一为“的”。 三、动宾短语 动宾之间是支配与被支配、关涉与被关涉的关系。动词＋宾语。宾语是回答动词“谁”、“什
么”、“哪儿”的。 例如：消灭敌人放下包袱丢下它发展生产进行斗争 骗取信任恢复平静爱热闹下决心有幽默感像珍珠 四、述补短语 A、动+补 动补短语中的补语不能回答动词“谁”、“什么”“哪儿”。 例如： 看清楚、去一趟、拿起来、引在脑子里、跑得快、走的急 五、形补短语 B、形+补 以形容词为中心时它的后面只有补语，因为形容词不能带宾语。结构助词“得”是补语的标志。 例如：机灵得很密得不透气漂亮极了 六、主谓短语 陈述与被陈述的关系。名词（代词）+动词（形容词） 主语可以回答谓语“谁”、“什么”；谓语可以回答主语“怎么样” 结构形式：A名+动B名+形C代+动D代+形 例如： 觉悟提高思想解放阳光灿烂心情舒畅 特殊主谓短语：名词做谓语。 例如： 今天星期三明天国庆节他中等身材 七、复指短语
1.感官动词用法之一：see, hear, listen to, watch, notice等词，后接宾语，再接动词原形或ing形式。前者表全过程，后者表正在进行。句中有频率词时，以上的词也常跟动词原形。 I heard someone knocking at the door when I fell asleep. (我入睡时有人正敲门) I heard someone knock at the door three times. (听的是全过程) I often watch my classmates play volleyball after school.(此处有频率词often) 若以上词用于被动语态，后面原有动词原形改为带to不定式： We saw him go into the restaurant. →He was seen to go into the restaurant. I hear the boy cry every day. →The boy is heard to cry every day. 2.感官动词用法之二：look, sound, smell, taste, feel可当系动词，后接形容词： He looks angry. It sounds good. The flowers smell beautiful. The sweets taste sweet. The silk feels soft. I felt tired. They all looked tired. 这些动词都不用于被动语态。如：The sweets are tasted sweet.是个病句。注意：如果加介词like,则后不可接形容词，而接名词或代词：
一汉语短语结构类型的分析 １．１自《马氏文通》问世以来，有关汉语语法的论著对短语的分类基本上是按外部功能和内部结构这两个标准来进行的，其中以内部结构为标准的分类占有更重要的地位。其实，汉语短语分类中的“功能说”和“结构说”都在一定程度上受到叶斯丕森和布龙菲尔德理论的影响。在结构分类方面，布氏的句法结构观念似乎特别适合于汉语，因为汉语词的构成方式、短语的构成方式和句子的构成方式是那样相似，以至布氏的句法结构类型的分析可以直接应用于汉语每一层面上的语法单位的结构分析。短语在汉语语法单位中处于一种枢纽地位，因此，短语的结构类型可以上通句子下至词。这是汉语语法单位进行结构分析的一条捷径，发展到顶峰就是“词组本位说”。如范晓先生在《说句子成分》、《关于结构和短语》①等文中多次提出：汉语的句子结构和短语结构的构造原则基本上是一致的，除独词句外，句子只不过是独立的短语而已。根据这种观点，应当是有多少种结构的短语，相应地便会有多少种结构的句子。 １．２“词组本位说”把句法结构类型和短语类型完全对应起来，即以分析短语的结构类型为基础，扩 展到句子结构。作为一种分析方法，它有可取之处；从实际的作业上看，它也具有相当的成效。它操作起来十分简便，似乎可以一以贯之地分析汉语的一切“结构”，然而从另一个角度看，恰恰是这种简便掩盖了汉语短语类型分析的句法分析中的一些实质性问题，如（一）是不是每个短语都可以在结构类型中找出它的归属？有的虚词和实词组合，其内部结构关系如何看待？（二）结构类型相同的短语，为什么其语法功能和转换关系不同？比如“人才交流”和“学者讨论”在结构分类中都是主谓关系，但前者能作“进行”类动词的宾语，后者不能；前者能在受定语限定之后作主语或宾语，后者不能。（三）许多结构类型不同的短语却有同样的语法功能，这是为什么？ 短语同词一样是静态的、备用的语法单位，对它内部进行分析以及据此而进行的分类，其标准与动态的、使用的语法单位—一句子的分析不应该是一样的，事实上，构成短语的成分和构成句子的成分也并不具有完全的同一性。吕叔湘先生认为“从语素到句子”有一个“中间站”，即短语。②这里我们借用下“中间站”这个说法。我们认为，如果说汉语语法单位由静态转化为动态有一个中间站的话，那末这个中间站不是短语，而是句子成分。语和短语都需要这个中间站的过渡，才能由静态的备用单位转化为动态的使用单位。③“词组本位说”所做的单纯的结构分析究其根源是混淆了两种不同性质的单位，因而没能解决上述问题，也就不能使短语研究向更深的方向发展。 正因如此，目前有些学者对“词组本位说”提出质疑，试图把短语的结构和句子的结构区别开来，进而建立词法、短语法（有的学者叫“下句法结构”）、句法三足鼎立的语法分析体系，④这一步迈得很勇敢，也颇有见地。如果把短语法单列出来，那末短语分类就和句法结构分类有了质的区别。但他们的分类如仍按短语内部的结构关系来确定，上面提出的问题就仍无法解决。 二短语分类的原则 ２．１为了解决上述问题，我们试图从一个新的角度来给短语分类。有一个原则问题必须加以强调，那就是同划分任何语法单位类别一样，给短语分类也应该遵守一个不可忽视的原则：划分出来的类别能够有效地服务于分析。反过来说，就是：不管用什么标准来划分，只要划分出来的类别可以用来有效地说明语法规律，这个分类就应该是有效的语法分类。 基于上述原则，就我们已经掌握的语言材料进行试验的结果来看，依据短语内部的语义关系进行的分类能够较好地服务于语法分析的目的，能够较好地解决至今尚未很好解决的一些句法分析问题，如句法分析中的主宾类问题。用这个新的分类能够较好地说明短语作为与词一样的静态单位，其内部语义关系的不同对它的句法功能以及对包括它在内的更大一级的句法结构有什么影响，而这些问题是依据结构关系分类所无法说明的。事实上，类似这种分类的观点已经有人在实际的语法分析中运用过，只不过是非自觉的罢了。比如许多学者分过“受事主语句”的特点，从这些分析中可以看出：在他们的意识中肯定是把“施事—一动作”格式和“受事—一动作”格式加以对比，而这两种格式正是从分析语义关系的角度确定的。我们不过是试图把这种零散的、不自觉地运用语义关系进行语法分析的做法当作一种理论依据加以系统化而已。２．２我们给短语分类的标准是词与词之间的语义关系。当然，语义是一个相当宽泛的概念，因此这里就需要给语义标准界定一个范围。如前所述，从分类的目的和结果来看，以语义关系为标准的分类也应该
短语的结构分类 [口诀]短语看结构，十种莫忧愁。并偏动介补，主的兼连固。 1、并列短语 词语之间互不修饰限，地位平等，这样的短语就是并列短语，也称为“联合短语”。 这类短语主要由名词、动词、形容词、代词、数量词这四种词语自我构成，或者几种词语搭配构成，主要有五种形式，可以简单表示为：n.+ n./v.+ v./adj.+ adj./pron.+ pron./aum.+ aum.， 例如：崇山峻岭柴米油盐思想感情民俗风情老师和同学国家与集体个人与社会 发展变化研究决定调查研究总结推广吃喝穿戴继承和发扬继承与创新 婉转悠扬和谐幸福金碧辉煌富丽堂皇庄严肃穆丰富而富饶光荣而艰巨 你、我、他你和我这门那户这个那个彼此彼此谁谁谁一个和八个二百五 2、偏正短语 词语之间有修饰限制关系，前一个词语对后一个词语进行修饰和限制，而以后一个词语为中心，词语与词语之间是偏正关系，这样的短语是偏正短语。修饰名词的词叫定语，用（）来表示；修饰动词、形容词的词叫状语，用〔〕来表示。这类短语主要以名词、动词、形容词为主体构成，主要有三种形式，简单记为：adj.+ n./adv.+ v./adv.+ adj.，例如：（1）名词性偏正短语——定语+名词（或代词） ①名词、代词、动词、形容词作定语。例如： 名+名：中华情赤壁赋出师表兰亭集序荷塘月色故都的秋赤壁之战 代+名：我们家这个人之二虫这只黄鹂那只白鹭这条纱巾那根拐棍 动+名：发言稿止痛片美发厅调查提纲训练计划运动规律游览路线 形+名：黑牡丹红太阳白玫瑰绿色食品经典作品优秀分子永恒魅力 ②指示代词、数词、量词组合作定语。 例如：（指+数+量）+名：这支笔这一位委员那一个书包这两个人那一年六月 （数+量）+名：七根火柴一年四季一件小事一曲窦娥冤千古关汉卿 （2）动词性偏正短语——状语+动词 ①状语表示的意义 状语可以表示动作、行为的情态、时间、频率、范围、处所、对象等。例如： 表示情态：努力进取认真研究大力发展倾情奉献喜闻乐见娓娓动听 表示时间：猝死马上出发立刻行动现在开始从眼前抓起于拂晓结束 表示频率：间进经常说寻常见几度闻一再强调再三叮嘱常来常往 表示范围：都好全赖一呼百应一丝不挂九九归一根根寄梦个个宁腮 表示处所：东进外敷向阳开内引外联上窜下跳外树形象内抓管理 表示对象：天问东向坐今日始把根留住将心比心对天发誓向隅而泣 ②状语的构成
专题三短语结构复习题 1．(2014·潍坊中考)下列各组短语，结构类型不同的一项是( ) A．雄伟壮丽根深蒂固廉明公正舍生取义 B. 非常坚强自知之明万贯家私长途跋涉 C. 精力充沛盛气凌人夸父逐日愚公移山 D. 敬畏生命包罗万象鼎力相助不见天日 2．(2017·潍坊模拟)下列各句，表述正确的一项是( ) A．“前面”“后面”“十笏园”“范畴”“死板”都是名词。 B．“露珠晶莹”“心情愉快”“敬畏生命”“红得发紫”都是主谓短语。 C．“那些模样最像武士脸型的蟹就得天独厚地生存下来”主干是“蟹生存”。 D．“我们家的台阶有三级”中，“我们家的”是状语。 3．(2017·潍坊模拟)下列句子中画线短语与例句画线短语结构相同的一项是 ( ) 例句：全桥结构匀称，和四周景色配合得十分和谐。 A．中国的大豆闻名世界，中国也被誉为“大豆王国”。 B．统筹方法，是一种合理安排工作进程的数学方法。 C．以圣母殿为主体的建筑群，造型古朴优美，做工精巧。 D．一个共产党员，应该襟怀坦白，忠实，积极。 4．(2017·潍坊模拟)对下列短语类型辨析不正确的一项是( ) A．回忆我的母亲(偏正短语) 藤野先生(并列短语) B．勤劳俭朴(并列短语) 狼吞虎咽(并列短语) C．性格和蔼(主谓短语) 祖国富强(主谓短语) D．追求光明(动宾短语) 精通时事(动宾短语) 5．(2017·潍坊模拟)下列短语结构方式不相同的一组是( ) A．性格和蔼樱花烂漫前程万里舆论沸腾 B. 精通时事横渡长江翻检一通发表成绩 C. 革命征途热烈鼓掌祖国大地分外妖娆 D. 宽厚仁慈勤劳俭朴德高望重朝晖夕阴 参考答案 1．D 【解析】 A．都是并列短语；B.都是偏正短语；C.都是主谓短语；D.“鼎力相助”是偏正短语，其余是动宾短语。 2．C 【解析】 A．“死板”是形容词；B.“敬畏生命”是动宾短语，“红得发紫”是后补短语； D.“我们家的”是定语。 3．D 【解析】“结构匀称”是主谓短语。A.“闻名世界”是后补短语；B.“统筹方法”是偏正短语； C.“古朴优美”是并列短语； D.“襟怀坦白”是主谓短语。 4．A 【解析】“回忆我的母亲”是动宾短语，“藤野先生”是偏正短语。 5．B 【解析】 A．都是主谓短语；B.“翻检一通”是后补短语，其他三项是动宾短语；C.都是偏正短语；D.都是并列短语。 1
语文短语结构类型 一、并列短语 词和词之间没有轻重主次之分，彼此地位平等。 １、类型 ⑴名＋名文化教育今天或明天（名词短语） ⑵动＋动调查研究愿意并实行（动词短语） ⑶形＋形光辉灿烂庄严肃穆（形容词短语） ⑷代＋代我和他这样那样（名词短语） ⑸数量＋数量四面八方千秋万代三斤五两（名词短语） ２、并列短语一般前后可以互换位置。 例如：工厂农村我你他 但有些并列短语是不能前后颠倒位置的，因为它有一定次序。 ⑴时间顺序：春、夏、秋、冬 ⑵大小顺序：省、市、县 ⑶年龄顺序：老、中、青 ⑷逻辑顺序：继承和发展接近文学和爱好文学 ⑸语言习惯：男女老少金银铜铁油盐酱醋 ３、并列短语一般要求词性相同，但个别也有不同。 例如：姐姐和我（名词＋代词） 二、偏正短语 １、前偏后正：“偏”修饰、限制“正”。 ⑴定＋中（名、代），如：（祖国）大地（一朵）茶花（前进）的步伐 ⑵状＋中（动、形），如：[很]好看 [独立]思考 [慢慢]地走 ２、“的”是定语的标志；“地”是状语的标志。 三、动宾短语 动宾之间是支配与被支配、关涉与被关涉的关系。动词＋宾语。宾语是回答动词“谁”、“什么”、“哪儿”的。 例如：消灭敌人放下包袱丢下它发展生产进行斗争、 骗取信任恢复平静爱热闹下决心有幽默感像珍珠 四、动补短语 动+补 动补短语中的补语不能回答动词“谁”、“什么”“哪儿”。 例如：看清楚、去一趟、拿起来、引在脑子里 五、形补短语 形+补 以形容词为中心时它的后面只有补语，因为形容词不能带宾语。 结构助词“得”是补语的标志。 例如：跑得快走得急机灵得很密得不透气 六、主谓短语 陈述与被陈述的关系。名词（代词）+动词（形容词） 主语可以回答谓语“谁”、“什么”；谓语可以回答主语“怎么样” 例如：觉悟提高思想解放阳光灿烂心情舒畅