<?xml version="1.0" encoding="UTF-8"?>

  <rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns="http://purl.org/rss/1.0/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
  >

  <channel rdf:about="http://ciscoarticles.com/rss/rss.php">
    <title>CCSP-Cisco Certified Security Professional</title>
    <link>http://ciscoarticles.com/rss/rss.php</link>
    <description></description>
    <dc:language>en-us</dc:language>
    <dc:rights>Copyright 2010, </dc:rights>
    <dc:publisher>rhifat@gmail.com</dc:publisher>
    <dc:creator>rhifat@gmail.com</dc:creator>
    <dc:title>CCSP-Cisco Certified Security Professional</dc:title>
    <dc:source>http://ciscoarticles.com/rss/rss.php</dc:source>
    <dc:type>Collection</dc:type>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>4</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Named Access Lists networks.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/ICMP-Access-Lists.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/UDP-Access-Lists.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/TCP-Access-Lists.html" />
        <rdf:li rdf:resource="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/4359.html" />
        
        
        
        
        
        
        
        
        
        
                
      </rdf:Seq>
    </items>
  </channel>
  <item rdf:about="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Named Access Lists networks.html">
<title>Named Access Lists</title>
<link>http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/Named Access Lists networks.html</link>
<description>  
&lt;a name=&quot;2030&quot; /&gt;&lt;a name=&quot;wbp33AppAP361&quot; /&gt;&lt;a name=&quot;wbp33AppAP361&quot;&gt;  &lt;/a&gt;
&lt;a name=&quot;wbp33AppAP361&quot;&gt;Since Cisco IOS Release 11.2, you can use a text name for   access lists in many cases. Some new features have been added to named ACLs that   make them more than just text names. The benefits ...</description>
<dc:language>en-us</dc:language>
<dc:title>Named Access Lists</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=4363</dc:source>
<dc:rights>Copyright 2010, </dc:rights>
<dc:date>2010-03-24T00:00:00+03:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/ICMP-Access-Lists.html">
<title>ICMP Access Lists</title>
<link>http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/ICMP-Access-Lists.html</link>
<description>
 
ICMP (Internet Control Message Protocol&amp;#8212;RFC 792) access list 
syntax doesn&amp;#8217;t use port numbers, but adds options to allow filtering on ICMP 
messages. The actual syntax for filtering UDP is as follows:
access-list &lt;i class=&quot;emphasis&quot;&gt;acl#&lt;/i&gt; {permit | deny} icmp 
{&lt;i class=&quot;emphasis&quot;&gt;source&lt;/i&gt; &lt;i class=&quot;emphasis&quot;&gt;wildcard&lt;/i&gt; | any} {&lt;i class=&quot;emphasis&quot;&gt;destination wildcard&lt;/i&gt; |any} [&lt;i class=&quot;emphasis&quot;&gt;icmp-type&lt;/i&gt; ...</description>
<dc:language>en-us</dc:language>
<dc:title>ICMP Access Lists</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=4362</dc:source>
<dc:rights>Copyright 2010, </dc:rights>
<dc:date>2010-03-24T00:00:00+03:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/UDP-Access-Lists.html">
<title>UDP Access Lists</title>
<link>http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/UDP-Access-Lists.html</link>
<description>
 
The &lt;i class=&quot;emphasis&quot;&gt;UDP access list, &lt;/i&gt;like TCP, 
supports both source and destination ports, and, like TCP, uses the same 
relational operators to define the mnemonic or port numbers. The following code 
output shows some of the most common UDP port names:
 Rtr1(config)#access-list 101 permit udp any eq ?  ...</description>
<dc:language>en-us</dc:language>
<dc:title>UDP Access Lists</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=4361</dc:source>
<dc:rights>Copyright 2010, </dc:rights>
<dc:date>2010-03-24T00:00:00+03:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/TCP-Access-Lists.html">
<title>TCP Access Lists</title>
<link>http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/TCP-Access-Lists.html</link>
<description> 
TCP access lists support both source and destination TCP 
ports, which can be specified using either the port number or mnemonic. Port 
numbers or name must be preceded with relational operators, such as those shown 
in the following code output: Rtr1(config)#access-list 101 deny tcp host 10.0.0.97 ?  &amp;#160;eq ...</description>
<dc:language>en-us</dc:language>
<dc:title>TCP Access Lists</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=4360</dc:source>
<dc:rights>Copyright 2010, </dc:rights>
<dc:date>2010-03-24T00:00:00+03:00</dc:date>
<dc:type>text</dc:type>
</item>

  <item rdf:about="http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/4359.html">
<title>Extended Access Lists</title>
<link>http://ciscoarticles.com/CCSP-Cisco-Certified-Security-Professional/4359.html</link>
<description>&lt;a name=&quot;2019&quot; /&gt;&lt;a name=&quot;wbp33AppAP186&quot; /&gt;&lt;a name=&quot;2020&quot; /&gt;&lt;a name=&quot;IDX-965&quot; /&gt;
&lt;i class=&quot;emphasis&quot;&gt;Extended access lists&lt;/i&gt; provide a higher level 
of traffic control by being able to filter packets based on the protocol, source 
and/or destination IP address, and source and/or destination port number. For 
example, an extended access list can block an address ...</description>
<dc:language>en-us</dc:language>
<dc:title>Extended Access Lists</dc:title>
<dc:source>http://ciscoarticles.com/rss/article_view.php?articleId=4359</dc:source>
<dc:rights>Copyright 2010, </dc:rights>
<dc:date>2010-03-24T00:00:00+03:00</dc:date>
<dc:type>text</dc:type>
</item>

  
  
  
  
  
  
  
  
  
  
  
</rdf:RDF>
